Firmware integrity compromise via unchecked EFI variable
Published Aug 7, 2023 · Updated Mar 7, 2025
Improper input validation in Insyde InsydeH2O kernels 5.0 through 5.5 allows local users to compromise firmware integrity via an EFI variable. The TSEG overlap check accepts attacker-controlled values from a runtime-accessible EFI variable when assigning a dynamic Base Address Register, allowing the resulting range to overlap System Management RAM. The attack requires low-privilege local access and permits unauthorized modification of protected memory and a service interruption.
Summary
What happened
Improper input validation in Insyde InsydeH2O kernels 5.0 through 5.5 allows local users to compromise firmware integrity via an EFI variable. The TSEG overlap check accepts attacker-controlled values from a runtime-accessible EFI variable when assigning a dynamic Base Address Register, allowing the resulting range to overlap System Management RAM. The attack requires low-privilege local access and permits unauthorized modification of protected memory and a service interruption.
The record
- CVE
- CVE-2023-27373
- Published
- Aug 7, 2023
- Updated
- Mar 7, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-20, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 7, 2023CVE publishedPublication date reported by the CVE source.
- Mar 7, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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