forcedotcom SalesforceMobileSDK-Windows up to 4.x QuerySpec.cs ComputeCountSql sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in forcedotcom SalesforceMobileSDK-Windows up to 4.x and classified as critical. The affected element is the function ComputeCountSql of the file SalesforceSDK/SmartStore/Store/QuerySpec.cs. The manipulation leads to sql injection. This vulnerability only affects products that are no longer supported by the maintainer.
This vulnerability is traded as CVE-2016-15012. There is no exploit available.
The affected component should be upgraded.
Details
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 with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability.
The weakness was shared 01/07/2023 as 83b3e91e0c1e84873a6d3ca3c5887eb5b4f5a3d8. It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2016-15012. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.
Upgrading to version 5.0.0 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 83b3e91e0c1e84873a6d3ca3c5887eb5b4f5a3d8 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version. The advisory contains the following remark:
use statement to build sql query to avoid the possibility for SQLi security risk
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
License
Support
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.9VulDB Meta Temp Score: 6.9
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CNA Base Score: 5.5
CNA Vector (VulDB): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: SalesforceMobileSDK-Windows 5.0.0
Patch: 83b3e91e0c1e84873a6d3ca3c5887eb5b4f5a3d8
Timeline
01/07/2023 🔍01/07/2023 🔍
01/07/2023 🔍
08/06/2024 🔍
Sources
Product: github.comAdvisory: 83b3e91e0c1e84873a6d3ca3c5887eb5b4f5a3d8
Status: Confirmed
CVE: CVE-2016-15012 (🔍)
GCVE (CVE): GCVE-0-2016-15012
GCVE (VulDB): GCVE-100-217619
Entry
Created: 01/07/2023 14:04Updated: 08/06/2024 10:14
Changes: 01/07/2023 14:04 (46), 01/29/2023 22:39 (2), 01/29/2023 22:53 (28), 01/29/2023 23:05 (1), 08/06/2024 10:14 (22)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.