Authentication bypass via unauthenticated PHT reuse
Published Apr 27, 2022 · Updated Sep 16, 2024
Authentication bypass in AMD Zynq-7000 SoC FSBL 2021.2 through 2022.1 allows attackers to load malicious images via physical access. The FSBL retrieves partition header table data twice and then uses the second, unauthenticated copy when validating boot content. Physical possession and precise manipulation of boot storage are required, enabling execution of unauthorized code and potential decryption-oracle use.
Summary
What happened
Authentication bypass in AMD Zynq-7000 SoC FSBL 2021.2 through 2022.1 allows attackers to load malicious images via physical access. The FSBL retrieves partition header table data twice and then uses the second, unauthenticated copy when validating boot content. Physical possession and precise manipulation of boot storage are required, enabling execution of unauthorized code and potential decryption-oracle use.
The record
- CVE
- CVE-2022-23822
- Published
- Apr 27, 2022
- Updated
- Sep 16, 2024
- Vendor
- AMD
- Product
- Zynq-7000 SoC FSBL
- Classifications
- CWE-863, T1542.001
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 27, 2022CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=2021.2 <=2022.1
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.
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