Google Android PKCS#1 Signature Validator signature verification
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Google Android and classified as problematic. The impacted element is an unknown function of the component PKCS#1 Signature Validator. The manipulation leads to signature verification. This vulnerability is referenced as CVE-2014-9934. The attack can only be performed from a local environment. No exploit is available. The affected component should be upgraded.
Details
A vulnerability, which was classified as problematic, has been found in Google Android (Smartphone Operating System) (the affected version unknown). This issue affects an unknown part of the component PKCS#1 Signature Validator. The manipulation with an unknown input leads to a signature verification vulnerability. Using CWE to declare the problem leads to CWE-347. The product does not verify, or incorrectly verifies, the cryptographic signature for data. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
A PKCS#1 v1.5 signature verification routine in all Android releases from CAF using the Linux kernel may not check padding.
The bug was discovered 05/01/2017. The weakness was published 05/16/2017 (Website). The advisory is shared at source.android.com. The identification of this vulnerability is CVE-2014-9934 since 03/01/2017. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 15 days. During that time the estimated underground price was around $5k-$25k.
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 97329†). Similar entries are available at VDB-99354, VDB-99375, VDB-99376 and VDB-99383. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔍
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: Signature verificationCWE: CWE-347 / CWE-345
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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: 🔍
Timeline
03/01/2017 🔍04/03/2017 🔍
05/01/2017 🔍
05/16/2017 🔍
05/16/2017 🔍
05/17/2017 🔍
12/24/2020 🔍
Sources
Vendor: google.comAdvisory: source.android.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2014-9934 (🔍)
GCVE (CVE): GCVE-0-2014-9934
GCVE (VulDB): GCVE-100-101405
SecurityFocus: 97329 - Google Android Qualcomm components Multiple Unspecified Security Vulnerabilities
OSVDB: - CVE-2014-9934 - Google - Android - High
SecurityTracker: 1038201
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 05/17/2017 07:57Updated: 12/24/2020 14:13
Changes: 05/17/2017 07:57 (67), 12/24/2020 14:13 (2)
Complete: 🔍
Cache ID: 216:6A6:103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.