CVE-2022-24350
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 IhisiSmm in Insyde InsydeH2O with kernel 5.0 through 5.5. IHISI function 0x17 verifies that the output buffer lies within the command buffer but does not verify that output data does not go beyond the end of the command buffer. In particular, the GetFlashTable function is called directly on the Command Buffer before the DataSize is check, leading to possible circumstances where the data immediately following the command buffer could be destroyed before returning a buffer size error.
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 buffer overflow vulnerability in InsydeH2O UEFI firmware (kernel 5.0-5.5) in the IHISI SMM function 0x17. The function verifies output buffer location but fails to validate that output data stays within command buffer boundaries. The GetFlashTable function is called before DataSize validation, allowing writes beyond buffer end to corrupt adjacent memory.
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.0, <= 5.5CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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.
-
Retrieve UEFI firmware versionRun 'dmidecode -s bios-version' on Linux or 'wmic bios get SMBIOSBIOSVersion' on Windows to get the BIOS/UEFI firmware version stringAffected if The version string contains 'InsydeH2O' or 'Insyde' with a kernel version between 5.0 and 5.5
-
Extract InsydeH2O kernel versionParse the firmware version string to locate the InsydeH2O kernel number. The format typically includes the kernel version (e.g., '5.0', '5.2', '5.5') as part of the full version identifierAffected if The extracted kernel version falls within the range >= 5.0 and <= 5.5
-
Confirm vendor and modelRun 'dmidecode -s system-manufacturer' and 'dmidecode -s system-product-name' to identify the system vendor and model, as InsydeH2O is used by multiple OEMsAffected if The system uses InsydeH2O UEFI firmware with a kernel version in the affected range
-
Verify IHISI SMM availabilityThis requires examining the UEFI firmware binary or using vendor-specific tools. IHISI (Insyde Hardware Initialization and Security Interface) SMM function 0x17 is a proprietary function; no standard tool directly queries its presence. The vulnerability is in the GetFlashTable code path within this functionAffected if The system runs InsydeH2O firmware and the IHISI SMM function 0x17 is implemented (which is the case for most InsydeH2O implementations)
If the InsydeH2O kernel version extracted from the UEFI firmware version is 5.0, 5.1, 5.2, 5.3, 5.4, or 5.5, the system is within the affected version range and potentially vulnerable to the buffer overflow in IHISI SMM function 0x17.
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.
From vendor dataApply vendor-supplied firmware updates from Insyde/OEM partners. Until patches are available, limit physical access to affected systems and monitor for unauthorized firmware modifications.
- Consultation8.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,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24350 — 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-2022-24350 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