Modified BIOS installation via authenticity verification failure
Published Feb 9, 2022 · Updated Sep 16, 2024
Insufficient authenticity verification in Dell Client Platform BIOS before 1.15 allows local users to install modified firmware. Dell has not disclosed the verification locus or the operation that accepts attacker-controlled firmware as authentic. Exploitation requires local high privileges and replaces trusted platform firmware with attacker-modified BIOS code.
Summary
What happened
Insufficient authenticity verification in Dell Client Platform BIOS before 1.15 allows local users to install modified firmware. Dell has not disclosed the verification locus or the operation that accepts attacker-controlled firmware as authentic. Exploitation requires local high privileges and replaces trusted platform firmware with attacker-modified BIOS code.
The record
- CVE
- CVE-2022-22567
- Published
- Feb 9, 2022
- Updated
- Sep 16, 2024
- Vendor
- Dell
- Product
- Dell Client Platform BIOS
- Classifications
- CWE-345, T1542.001
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Feb 9, 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=unspecified <1.15
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