Physical service interruption via out-of-bounds write
Published Jun 23, 2023 · Updated Nov 7, 2024
Out-of-bounds write in Dell Client Platform BIOS allows physically proximate attackers to cause a service interrupt via physical access. Dell identifies the affected component only as BIOS and has not published the vulnerable firmware locus, input path, or incorrect bounds operation. Exploitation requires physical proximity but no authentication; the resulting interruption mode remains undisclosed.
Summary
What happened
Out-of-bounds write in Dell Client Platform BIOS allows physically proximate attackers to cause a service interrupt via physical access. Dell identifies the affected component only as BIOS and has not published the vulnerable firmware locus, input path, or incorrect bounds operation. Exploitation requires physical proximity but no authentication; the resulting interruption mode remains undisclosed.
The record
- CVE
- CVE-2023-28064
- Published
- Jun 23, 2023
- Updated
- Nov 7, 2024
- Vendor
- Dell
- Product
- Dell Client Platform BIOS
- Classifications
- CWE-787, T1499
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 23, 2023CVE publishedPublication date reported by the CVE source.
- Nov 7, 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=All Versions
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