CVE-2024-49200
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 AcpiS3SaveDxe and ChipsetSvcDxe in Insyde InsydeH2O with kernel 5.2 though 5.7. A potential DXE memory corruption vulnerability has been identified. The root cause is use of a pointer originating from the value of an NVRAM variable as the target of a write operation. This can be leveraged by an attacker to perform arbitrary writes, potentially leading to arbitrary code execution. The issue has been fixed in kernel 5.2, Version 05.29.44; kernel 5.3, Version 05.38.44; kernel 5.4, Version 05.46.44; kernel 5.5, Version 05.54.44; kernel 5.6, Version 05.61.44; and kernel 5.7, Version 05.70.44.
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 confidenceA DXE phase memory corruption vulnerability exists in AcpiS3SaveDxe and ChipsetSvcDxe components of Insyde InsydeH2O UEFI firmware. The flaw stems from using a pointer derived from an NVRAM variable value as the destination for write operations, enabling an attacker to perform arbitrary memory writes and potentially achieve arbitrary code execution in the DXE phase.
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.3= 5.4= 5.5= 5.6= 5.7CVSS 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
- Network
- Complexity
- High
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N
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 UEFI firmware versionOn Linux, run `dmidecode -s bios-version` or check system firmware information through `fwupdctl get-devices`. On Windows, check via `wmic bios get smbiosbiosversion` or in System Information under BIOS version.Affected if The reported firmware version corresponds to kernel 5.2, 5.3, 5.4, 5.5, 5.6, or 5.7 (exact versions without the fixed patches listed in the advisory).
-
Confirm the firmware vendor is InsydeCheck the system BIOS/UEFI vendor information using `dmidecode -s bios-vendor` on Linux or via System Information on Windows. InsydeH2O systems will report 'Insyde' as the vendor.Affected if The firmware vendor is Insyde and the kernel version matches one of the affected versions listed.
-
Determine the exact kernel version from firmwareThe InsydeH2O kernel version is often displayed in the UEFI setup under 'BIOS Version' or 'Firmware Version' and may include a kernel number (e.g., 5.2.xx). Cross-reference with Insyde's release notes or firmware patch documentation if available.Affected if The kernel version displayed is exactly 5.2, 5.3, 5.4, 5.5, 5.6, or 5.7 without the fixed patch versions (44 or later in each respective branch).
-
Verify the system uses the affected DXE componentsThis CVE affects AcpiS3SaveDxe and ChipsetSvcDxe components in the DXE phase. These are internal UEFI modules typically present on Insyde-based systems that implement ACPI S3 sleep state handling and chipset services. No user-facing tool directly lists these, but their presence can be inferred from the firmware being in the affected kernel versions.Affected if The firmware runs an affected kernel version (5.2 through 5.7), meaning these components are likely present and vulnerable.
A system is affected if it runs InsydeH2O UEFI firmware with kernel versions 5.2, 5.3, 5.4, 5.5, 5.6, or 5.7 that has not been updated to the respective fixed patch versions (44 or later in each branch).
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 · scopedUpdate the InsydeH2O firmware to one of the fixed versions: kernel 5.2 (05.29.44 or later), 5.3 (05.38.44 or later), 5.4 (05.46.44 or later), 5.5 (05.54.44 or later), 5.6 (05.61.44 or later), or 5.7 (05.70.44 or later).
InsydeH2O kernel 5.2 >= 05.29.44, 5.3 >= 05.38.44, 5.4 >= 05.46.44, 5.5 >= 05.54.44, 5.6 >= 05.61.44, or 5.7 >= 05.70.44
- Identify the current InsydeH2O kernel version by checking the system firmware/UEFI version in the BIOS setup or via system information tools
- Contact the hardware OEM/vendor (not Insyde directly) to obtain the appropriate firmware update containing the fixed kernel version
- For kernel 5.2, request firmware Version 05.29.44 or later; for kernel 5.3, request Version 05.38.44 or later; for kernel 5.4, request Version 05.46.44 or later; for kernel 5.5, request Version 05.54.44 or later; for kernel 5.6, request Version 05.61.44 or later; for kernel 5.7, request Version 05.70.44 or later
- Apply the firmware update following the OEM's documented firmware update procedure, ensuring stable power throughout the process
- Verify the firmware was successfully updated by checking the BIOS/UEFI version after the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49200 — 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-2024-49200 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