CVE-2023-28073
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 authentication vulnerability. A locally authenticated malicious user may potentially exploit this vulnerability by bypassing certain authentication mechanisms in order to elevate privileges on the system.
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 · moderate confidenceDell BIOS contains an improper authentication vulnerability where a locally authenticated malicious user can bypass certain authentication mechanisms to elevate privileges on the system. The vulnerability exists in the BIOS authentication subsystem, allowing privilege escalation from a standard user to higher privileges.
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.13.2< 1.13.2CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 modelRun 'systeminfo' or 'wmic computersystem get model' from command prompt to determine if the system is a Dell Precision 3570 or Latitude 5530Affected if The system model is Dell Precision 3570 or Latitude 5530
-
Check the installed BIOS firmware versionRun 'wmic bios get smbiosbiosversion' or use Dell Command | Configure (if available) to retrieve the current BIOS versionAffected if The BIOS version is below 1.13.2 (e.g., 1.13.1, 1.12.0, etc.)
-
Verify the system has local user accounts configuredCheck for local user accounts using 'net user' or review Local Users and Groups in Computer ManagementAffected if Local user accounts exist on the system (the vulnerability enables a standard local user to escalate privileges)
You are affected if you are running a Dell Precision 3570 or Latitude 5530 with BIOS firmware version earlier than 1.13.2, and the system has local user authentication enabled.
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.13.2
Apply the Dell BIOS/firmware update provided by Dell for affected systems. This is a vendor-supplied patch that must be obtained from Dell's support portal and applied following their specific update procedures.
BIOS Firmware version 1.13.2 or later for Precision 3570 and Latitude 5530
- Navigate to Dell's support website (www.dell.com) and locate the drivers and downloads section for your specific model (Precision 3570 or Latitude 5530)
- Download the BIOS update file for version 1.13.2 or later
- Run the downloaded BIOS update executable or extract the firmware update files
- Follow the on-screen prompts to update the BIOS firmware, ensuring the system remains powered throughout the process
- Restart the system after the update completes to ensure the new BIOS version is properly loaded
- Verify the BIOS version has been updated to 1.13.2 or later by checking the BIOS setup or using system information tools
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.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,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28073 — 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-28073 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