CVE-2023-34195
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue was discovered in SystemFirmwareManagementRuntimeDxe in Insyde InsydeH2O with kernel 5.0 through 5.5. The implementation of the GetImage method retrieves the value of a runtime variable named GetImageProgress, and later uses this value as a function pointer. This variable is wiped out by the same module near the end of the function. By setting this UEFI variable from the OS to point into custom code, an attacker could achieve arbitrary code execution in the DXE phase, before several chipset locks are set.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe SystemFirmwareManagementRuntimeDxe module in InsydeH2O kernel 5.0-5.5 has a vulnerability in its GetImage method where it retrieves a runtime UEFI variable named 'GetImageProgress' and uses its value directly as a function pointer without validation. Since an attacker with OS-level privileges can set this variable from the operating system, they can redirect execution to arbitrary code in the DXE boot phase before chipset locks engage.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 5.2, < 5.2.05.28.22>= 5.3, < 5.3.05.37.22>= 5.4, < 5.4.05.45.22>= 5.5, < 5.5.05.53.22>= 5.6, < 5.6.05.60.22CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the InsydeH2O firmware versionRun 'dmidecode -s bios-version' or check the firmware version through the UEFI/BIOS setup menu. On Linux, you can also use 'cat /sys/class/dmi/id/bios_version'Affected if The version falls within any of these ranges: >= 5.2 and < 5.2.05.28.22; >= 5.3 and < 5.3.05.37.22; >= 5.4 and < 5.4.05.45.22; >= 5.5 and < 5.5.05.53.22; >= 5.6 and < 5.6.05.60.22
-
Verify the SystemFirmwareManagementRuntimeDxe module is presentExtract and inspect the UEFI firmware ROM image using tools like UEFITool or flashrom. Search for the module named 'SystemFirmwareManagementRuntimeDxe' in the DXE driver sectionAffected if The module exists in the firmware and its version is vulnerable based on the kernel version ranges above
-
Check the GetImageProgress UEFI runtime variableUse a tool like 'efi-readvar' on Linux or 'ruvap' to enumerate UEFI runtime variables. Look for a variable named 'GetImageProgress'. Note that its presence alone does not indicate exploitation, but the variable can be set from the OS if the firmware is vulnerableAffected if The runtime variable 'GetImageProgress' exists in the system's UEFI variable store and can be manipulated from the operating system
-
Confirm the GetImage method implementationDisassemble or analyze the SystemFirmwareManagementRuntimeDxe driver extracted from the firmware. Verify if the GetImage method uses the GetImageProgress variable value as a function pointer without validationAffected if The driver uses the GetImageProgress variable value directly as a function pointer without sanity checks in the GetImage method
You are affected if your InsydeH2O firmware version is within any of the listed vulnerable ranges AND the SystemFirmwareManagementRuntimeDxe module uses the GetImageProgress variable as an unvalidated function pointer.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped5.2.05.28.225.3.05.37.225.4.05.45.22
Apply the vendor firmware update from Insyde. Until then, restrict physical access and privileged OS access to prevent malicious UEFI variable manipulation; monitor for unauthorized firmware modifications.
Upgrade to one of: 5.2.05.28.22 or later (5.2.x branch), 5.3.05.37.22 or later (5.3.x branch), 5.4.05.45.22 or later (5.4.x branch), or 5.5.05.53.22 or later (5.5.x branch)
- Identify the current InsydeH2O firmware version installed on the affected system (typically shown in UEFI/BIOS setup or during boot)
- Determine which version branch the current firmware belongs to (5.2, 5.3, 5.4, or 5.5 series)
- Obtain the appropriate fixed firmware version from the system OEM or Insyde: for 5.2.x branch use version >= 5.2.05.28.22; for 5.3.x use >= 5.3.05.37.22; for 5.4.x use >= 5.4.05.45.22; for 5.5.x use >= 5.5.05.53.22
- Apply the firmware update using the OEM's recommended update process (typically via BIOS update utility, USB flash, or in-band update mechanism)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation40.0 h
- Testing24.0 h
- Review / QA16.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $24,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-34195 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-34195 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data