CVE-2022-24417
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 · uneditedDell BIOS contains an improper input validation vulnerability. A local authenticated malicious user may potentially exploit this vulnerability by using an SMI to gain arbitrary code execution during SMM.
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 confidenceDell BIOS has an improper input validation vulnerability that allows a local authenticated attacker to use a System Management Interrupt (SMI) to achieve arbitrary code execution in System Management Mode (SMM). SMM operates at the highest privilege level, making this a serious firmware-level flaw despite the medium CVSS score.
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< 1.10.0< 1.8.0< 1.8.0< 2.15.0< 1.4.4< 1.4.4< 1.4.1< 1.5.0CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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 your Dell system modelCheck the system label, BIOS startup screen, or use system information utilities (dmidecode -s system-product-name on Linux, or systeminfo on Windows) to confirm the exact model numberAffected if The model is not one of the listed affected products (Dell G5 5505, Inspiron 22 3275, Inspiron 24 3475, Inspiron 27 7775, Inspiron 3180, Inspiron 3185, Inspiron 3195, or Inspiron 3505)
-
Determine the installed BIOS firmware versionAccess the BIOS setup (press F2 at startup), or retrieve via command line: dmidecode -s bios-version on Linux, wmic bios get version on Windows, or Dell SupportAssist/Update utilityAffected if Unable to retrieve a version number - the system may be running an older or custom BIOS that does not report version information standardly
-
Compare your firmware version against affected thresholdsCross-reference the installed version with the vulnerable version thresholds: G5 5505 < 1.10.0, Inspiron 22 3275 < 1.8.0, Inspiron 24 3475 < 1.8.0, Inspiron 27 7775 < 2.15.0, Inspiron 3180/3185 < 1.4.4, Inspiron 3195 < 1.4.1, Inspiron 3505 < 1.5.0Affected if Your installed version is lower than the threshold listed for your specific model (e.g., G5 5505 on 1.5.0 is affected, but 1.10.0 or higher is not)
-
Verify the attacker would need local authenticated accessConfirm this vulnerability requires a local authenticated attacker - the system must already be accessible with valid credentials to log into the operating systemAffected if Your system is not protected by login authentication or allows unauthorized physical access to untrusted individuals
You are affected if you own a Dell G5 5505, Inspiron 22 3275, Inspiron 24 3475, Inspiron 27 7775, Inspiron 3180, Inspiron 3185, Inspiron 3195, or Inspiron 3505 and your current BIOS firmware version is below the version threshold listed for your model.
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 · scoped1.4.11.4.41.5.0
Apply the Dell BIOS firmware update for affected systems. Restrict physical access and ensure proper authentication controls are in place to prevent unauthorized local access until the patch is deployed.
Firmware version 1.10.0 (G5 5505), 1.8.0 (Inspiron 22 3275/24 3475), 2.15.0 (Inspiron 27 7775), 1.4.4 (Inspiron 3180/3185), 1.4.1 (Inspiron 3195), or 1.5.0 (Inspiron 3505)
- Identify the exact Dell model from the affected product list (G5 5505, Inspiron 22 3275, Inspiron 24 3475, Inspiron 27 7775, Inspiron 3180, Inspiron 3185, Inspiron 3195, or Inspiron 3505)
- Navigate to Dell support website (www.dell.com) and locate the BIOS update page for the specific model
- Download the BIOS firmware update: version 1.10.0 for G5 5505; 1.8.0 for Inspiron 22 3275 and Inspiron 24 3475; 2.15.0 for Inspiron 27 7775; 1.4.4 for Inspiron 3180 and Inspiron 3185; 1.4.1 for Inspiron 3195; 1.5.0 for Inspiron 3505
- Connect the system to AC power and ensure the update process will not be interrupted
- Run the Dell BIOS update utility and follow the on-screen instructions to flash the BIOS
- Allow the system to restart and complete the BIOS update process
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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 $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24417 — 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-24417 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