CVE-2023-32467
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 Edge Gateway BIOS, versions 3200 and 5200, contains an out-of-bounds write vulnerability. A local authenticated malicious user with high privileges could potentially exploit this vulnerability leading to exposure of some UEFI code, leading to arbitrary code execution or escalation of privilege.
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 Edge Gateway BIOS versions 3200 and 5200 contain an out-of-bounds write vulnerability that allows a local authenticated attacker with high privileges to potentially expose UEFI code and achieve arbitrary code execution or privilege escalation.
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= 0.1.19.0= 0.1.19.0< 1.05.10all versions= 0.1.13.0= 0.1.13.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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/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 Dell system modelRun 'dmidecode -s system-product-name' on Linux or check the system label/BIOS info screen on boot to confirm the model is one of: Edge Gateway 3200, 5000, 5100, 5200, XPS 13 9350, or Chengming 3977Affected if The system model is NOT one of these six models, then it is not affected by this specific CVE
-
Check the installed BIOS/firmware versionRun 'dmidecode -s bios-version' on Linux, 'systeminfo | findstr /C:"BIOS Version"' on Windows, or access the BIOS setup screen during boot to read the firmware versionAffected if Unable to retrieve the BIOS version - cannot determine if affected
-
Compare version against affected ranges for Edge Gateway 3200If the system is Edge Gateway 3200, note that ALL firmware versions are affected per the CVEAffected if The system is an Edge Gateway 3200 with any firmware version installed - it is affected
-
Compare version against affected ranges for Edge Gateway 5200If the system is Edge Gateway 5200, compare the installed firmware version to 1.05.10 - versions lower than 1.05.10 are affectedAffected if The system is Edge Gateway 5200 with firmware version < 1.05.10 - it is affected
-
Compare version against affected ranges for Edge Gateway 5000/5100If the system is Edge Gateway 5000 or 5100, check if the firmware version is exactly 0.1.19.0Affected if The system is Edge Gateway 5000 or 5100 with firmware version = 0.1.19.0 - it is affected
-
Compare version against affected ranges for XPS 13 9350 and Chengming 3977If the system is Dell XPS 13 9350 or Chengming 3977, check if the firmware version is exactly 0.1.13.0Affected if The system is XPS 13 9350 or Chengming 3977 with firmware version = 0.1.13.0 - it is affected
The system is affected if it is a Dell Edge Gateway 3200 (any version), Edge Gateway 5200 (<1.05.10), Edge Gateway 5000/5100 (=0.1.19.0), XPS 13 9350 (=0.1.13.0), or Chengming 3977 (=0.1.13.0).
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 data1.05.10
Apply the vendor-supplied BIOS/firmware update from Dell to patch the vulnerability. As this is a BIOS-level flaw, traditional network controls provide no protection; physical/local access with administrative privileges is required for exploitation.
- 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-2023-32467 — 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-32467 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