CVE-2023-32472
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 code in System Management Mode, 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. A local authenticated attacker with high privileges can exploit this memory corruption issue in System Management Mode (SMM), potentially exposing SMM code and achieving 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 dataall versions< 1.05.10CVSS 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 your Dell Edge Gateway modelCheck the physical device label or access BIOS setup (press F2 during boot) to confirm the model number is either Edge Gateway 3200 or Edge Gateway 5200Affected if Model is not 3200 or 5200 (not affected)
-
Determine the installed firmware version on Edge Gateway 3200Access BIOS setup (F2 during boot) and navigate to the BIOS Information screen to read the firmware version, or use the Dell Command | Configure tool with 'cec get BIOS.Version'Affected if Any firmware version is installed (all versions affected per CVE)
-
Determine the installed firmware version on Edge Gateway 5200Access BIOS setup (F2 during boot) and navigate to the BIOS Information screen to read the firmware version, or use the Dell Command | Configure tool with 'cec get BIOS.Version'Affected if Firmware version is below 1.05.10 (affected)
-
Verify SMM is enabledAccess BIOS setup (F2 during boot) and check System Management Mode settings under Security or Advanced menus; confirm SMM is not disabledAffected if SMM is enabled and firmware version falls outside safe ranges (vulnerable to exploitation)
You are affected if you own an Edge Gateway 3200 with any firmware version, or an Edge Gateway 5200 with firmware version below 1.05.10, and SMM is enabled in BIOS settings.
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 for the Edge Gateway 3200 and 5200 models. This is a critical firmware-level vulnerability requiring BIOS update rather than software patching.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32472 — 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-32472 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