Snapdragon Auto, Snapdragon Compute…: Cleartext Storage of Sensitive Information
CVE-2022-22069 is a high-severity cleartext storage of sensitive information vulnerability in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables from Qualcomm, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 0.1% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on qualcomm.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Qualcomm | Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables | Not specified in the record | Not stated |
| Qualcomm | Aqt1000 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6390 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6391 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6420 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6421 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6426 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6430 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6431 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6436 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6574 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6574a Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6574au Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6595au Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6696 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qcm2290 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qcm4290 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qcm6490 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qcs2290 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qcs4290 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qcs6490 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qsm8350 Firmware | Not specified in the record | Not stated |
| Qualcomm | Sa6155 Firmware | Not specified in the record | Not stated |
| Qualcomm | Sa6155p Firmware | Not specified in the record | Not stated |
| Qualcomm | Sa8155 Firmware | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE; 35 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.7 | High | CNA (qualcomm.com) |
| CVSS 3.1 | 7.8 | High | NVD |
Official description
Devices with keyprotect off may store unencrypted keybox in RPMB and cause cryptographic issue in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Cleartext Storage of Sensitive Information
The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.
How developers prevent this class of flaw
- When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to encrypt the data at rest.
- In some systems/environments such as cloud, the use of double encryption (at both the software and hardware layer) might be required, and the developer might be solely responsible for both layers, instead of shared responsibility with the administrator of the broader system/environment.
More Cleartext Storage of Sensitive Information vulnerabilities (CWE-312)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables
- 7.0 High severity
- 9.8 Critical severity
- 7.8 High severity
- 9.8 Critical severity
- 7.8 High severity
- 7.8 High severity
Recent Cleartext Storage of Sensitive Information vulnerabilities
- 7.5 High severity
- 8.8 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.