Local PAuth bypass via weak signatures
Published Jun 4, 2020 · Updated Aug 4, 2024
Pointer Authentication weakness in QEMU allows local attackers to bypass ARM pointer protection on emulated systems. QEMU's ARM PAuth support signs every protected pointer with the same signature because its signature-generation routine fails to vary the signature input. A local attacker who obtains one protected-pointer signature can reuse it to bypass PAuth for programs running under QEMU; the issue affects versions 4.0.0 through before 5.0.0.
Summary
What happened
Pointer Authentication weakness in QEMU allows local attackers to bypass ARM pointer protection on emulated systems. QEMU's ARM PAuth support signs every protected pointer with the same signature because its signature-generation routine fails to vary the signature input. A local attacker who obtains one protected-pointer signature can reuse it to bypass PAuth for programs running under QEMU; the issue affects versions 4.0.0 through before 5.0.0.
The record
- CVE
- CVE-2020-10702
- Published
- Jun 4, 2020
- Updated
- Aug 4, 2024
- Vendor
- QEMU Project
- Product
- QEMU
- Classifications
- CWE-325
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 4, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=>= 4.0.0, < 5.0.0
What conditions does exploitation require?
What is affected?
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