Code execution via active debug code
Published Dec 5, 2023 · Updated Aug 2, 2024
Active debug code in Dell PowerEdge BIOS 1.4.4 allows physically proximate attackers to disclose or alter data, execute code, or interrupt service. Dell identifies the affected locus only as active debug code and does not disclose which firmware component or operation leaves it enabled. Physical access is required; successful exploitation can bypass firmware protections and compromise the server.
Summary
What happened
Active debug code in Dell PowerEdge BIOS 1.4.4 allows physically proximate attackers to disclose or alter data, execute code, or interrupt service. Dell identifies the affected locus only as active debug code and does not disclose which firmware component or operation leaves it enabled. Physical access is required; successful exploitation can bypass firmware protections and compromise the server.
The record
- CVE
- CVE-2023-44297
- Published
- Dec 5, 2023
- Updated
- Aug 2, 2024
- Vendor
- Dell
- Product
- PowerEdge BIOS
- Classifications
- CWE-1234, CWE-667
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 5, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 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=Version 1.4.4
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