Undetected firmware modification via unverified SPI flash
Published Nov 12, 2024 · Updated Nov 21, 2024
Improper firmware integrity validation in AMI Aptio V BKS_5.0 through BKS_5.37 allows physically proximate attackers to modify SPI flash. The firmware permits altered SPI flash contents to remain undetected because code integrity is not sufficiently verified; AMI has not disclosed the responsible verification path. Physical access and direct SPI-flash manipulation are required, and successful tampering can alter firmware data and interrupt platform operation.
Summary
What happened
Improper firmware integrity validation in AMI Aptio V BKS_5.0 through BKS_5.37 allows physically proximate attackers to modify SPI flash. The firmware permits altered SPI flash contents to remain undetected because code integrity is not sufficiently verified; AMI has not disclosed the responsible verification path. Physical access and direct SPI-flash manipulation are required, and successful tampering can alter firmware data and interrupt platform operation.
The record
- CVE
- CVE-2024-33660
- Published
- Nov 12, 2024
- Updated
- Nov 21, 2024
- Vendor
- American Megatrends International
- Product
- Aptio V
- Classifications
- CWE-494, T1542.001
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 12, 2024CVE publishedPublication date reported by the CVE source.
- Nov 21, 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=BKS_5.0 <=BKS_5.37
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