CVE-2016-15012
Last modified
CVE-2016-15012 is a critical-severity vulnerability rated 9.8/10 on the CVSS scale. ** UNSUPPORTED WHEN ASSIGNED ** A vulnerability was found in forcedotcom SalesforceMobileSDK-Windows up to 4.x. It has been rated as critical. EPSS estimates a 0.66% chance of exploitation in the next 30 days.
Description
** UNSUPPORTED WHEN ASSIGNED ** A vulnerability was found in forcedotcom SalesforceMobileSDK-Windows up to 4.x. It has been rated as critical. This issue affects the function ComputeCountSql of the file SalesforceSDK/SmartStore/Store/QuerySpec.cs. The manipulation leads to sql injection. Upgrading to version 5.0.0 is able to address this issue. The patch is named 83b3e91e0c1e84873a6d3ca3c5887eb5b4f5a3d8. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-217619. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Salesforce | Mobile Software Development Kit | < 5.0.0 |
References
- https://github.com/forcedotcom/SalesforceMobileSDK-Windows/commit/83b3e91e0c1e84873a6d3ca3c5887eb5b4f5a3d8Patch, Third Party Advisory
- https://github.com/forcedotcom/SalesforceMobileSDK-Windows/releases/tag/v5.0.0Release Notes, Third Party Advisory
- https://vuldb.com/?ctiid.217619Permissions Required, Third Party Advisory
- https://vuldb.com/?id.217619Permissions Required, Third Party Advisory
- https://github.com/forcedotcom/SalesforceMobileSDK-Windows/commit/83b3e91e0c1e84873a6d3ca3c5887eb5b4f5a3d8Patch, Third Party Advisory
- https://github.com/forcedotcom/SalesforceMobileSDK-Windows/releases/tag/v5.0.0Release Notes, Third Party Advisory
- https://vuldb.com/?ctiid.217619Permissions Required, Third Party Advisory
- https://vuldb.com/?id.217619Permissions Required, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2016-15012?
How severe is CVE-2016-15012?
How do I fix CVE-2016-15012?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2016
- CVE-2016-15007A vulnerability was found in Centralized-Salesforce-Dev-Fram…9.8
- CVE-2016-15008A vulnerability was found in oxguy3 coebot-www and classifie…6.1
- CVE-2016-15009A vulnerability classified as problematic has been found in …8.8
- CVE-2016-1501ownCloud Server before 8.0.9 and 8.1.x before 8.1.4 allow re…
- CVE-2016-15010** UNSUPPORTED WHEN ASSIGNED ** A vulnerability classified a…6.1
- CVE-2016-15011A vulnerability classified as problematic was found in e-Con…9.8
- CVE-2016-15013A vulnerability was found in ForumHulp searchresults. It has…9.8
- CVE-2016-15014A vulnerability has been found in CESNET theme-cesnet up to …5.5
- CVE-2016-15015A vulnerability, which was classified as problematic, was fo…5.3
- CVE-2016-15016A vulnerability was found in mrtnmtth joomla_mod_einsatz_sta…9.8
- CVE-2016-15017A vulnerability has been found in fabarea media_upload on TY…9.8
- CVE-2016-15018A vulnerability was found in krail-jpa up to 0.9.1. It has b…9.8
Are you affected by CVE-2016-15012?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
