Local firmware tampering via writable XBL_SEC region
Published Jun 2, 2020 · Updated Aug 5, 2024
Improper access control in Qualcomm Snapdragon XBL_SEC allows local users to modify secure-boot code and data on affected chipsets. The XBL_SEC memory region is assigned permissions that let a low-privileged caller overwrite its secure-boot code and data. Exploitation requires local low-privileged access and permits boot-flow manipulation, including suppressing the RAM-dump path by forcing a normal cold boot.
Summary
What happened
Improper access control in Qualcomm Snapdragon XBL_SEC allows local users to modify secure-boot code and data on affected chipsets. The XBL_SEC memory region is assigned permissions that let a low-privileged caller overwrite its secure-boot code and data. Exploitation requires local low-privileged access and permits boot-flow manipulation, including suppressing the RAM-dump path by forcing a normal cold boot.
The record
- CVE
- CVE-2019-14054
- Published
- Jun 2, 2020
- Updated
- Aug 5, 2024
- Vendor
- Qualcomm
- Product
- Snapdragon
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 2, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Kamorta, MSM8998, QCS404, QCS605, SDA660, SDA845, SDM630, SDM636, SDM660, SDM670, SDM710, SDM845, SDM850, SM8150, SXR1130, SXR2130
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo