Record corruption via improper length check
Published Oct 20, 2021 · Updated Aug 3, 2024
Integer overflow in Qualcomm QWES on affected Snapdragon chipsets allows local users to corrupt a protected record through local access. The TrustZone component applies an improper length check while updating the grace-period and count record, allowing the record-length calculation to wrap. Local access is required, but no prior privileges or separate user interaction are required; Qualcomm has not disclosed the exact post-overflow operation.
Summary
What happened
Integer overflow in Qualcomm QWES on affected Snapdragon chipsets allows local users to corrupt a protected record through local access. The TrustZone component applies an improper length check while updating the grace-period and count record, allowing the record-length calculation to wrap. Local access is required, but no prior privileges or separate user interaction are required; Qualcomm has not disclosed the exact post-overflow operation.
The record
- CVE
- CVE-2021-1913
- Published
- Oct 20, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-190
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 20, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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