CVE-2023-32453: Dell BIOS contains an improper authentication vulnerability.
Noroxi assessment
Priority: Monitor (action score 15/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
- Physical access to the device is required. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Dell BIOS contains an improper authentication vulnerability. A malicious user with physical access to the system may potentially exploit this vulnerability in order to modify a security-critical UEFI variable without knowledge of the BIOS administrator.
- Published
- Aug 16, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- CWE-287
Report tools
Action score
15
Monitor
Low priority for now.
- CVSS
- 15 / 40 · 3.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 3.9
- CNA · dell
- 4.6
- 0.7 point gap
CVSS:3.1/AV:P/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| dell | vostro 5491 | cpe:2.3:h:dell:vostro_5491 |
| dell | alienware m15 r7 firmware | cpe:2.3:o:dell:alienware_m15_r7_firmware |
| dell | alienware m15 r7 | cpe:2.3:h:dell:alienware_m15_r7 |
| dell | alienware m16 firmware | cpe:2.3:o:dell:alienware_m16_firmware |
| dell | alienware m16 | cpe:2.3:h:dell:alienware_m16 |
| dell | alienware m18 firmware | cpe:2.3:o:dell:alienware_m18_firmware |
| dell | alienware m18 | cpe:2.3:h:dell:alienware_m18 |
| dell | chengming 3900 firmware | cpe:2.3:o:dell:chengming_3900_firmware |
| dell | chengming 3900 | cpe:2.3:h:dell:chengming_3900 |
| dell | chengming 3901 firmware | cpe:2.3:o:dell:chengming_3901_firmware |
| dell | chengming 3901 | cpe:2.3:h:dell:chengming_3901 |
| dell | chengming 3910 firmware | cpe:2.3:o:dell:chengming_3910_firmware |
and 188 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- dell alienware m15 r7 firmwarebefore 1.18.0
- dell alienware m16 firmwarebefore 1.10.1
- dell alienware m18 firmwarebefore 1.10.1
- dell chengming 3900 firmwarebefore 1.15.0
- dell chengming 3901 firmwarebefore 1.15.0
- dell chengming 3910 firmwarebefore 1.6.0
- dell chengming 3911 firmwarebefore 1.6.0
- dell g15 5520 firmwarebefore 1.18.0
- dell g16 7620 firmwarebefore 1.18.0
- dell g3 3500 firmwarebefore 1.26.0
- dell g5 15 5500 firmwarebefore 1.26.0
- dell g7 15 7500 firmwarebefore 1.26.0
- dell g7 17 7700 firmwarebefore 1.26.0
- dell inspiron 14 5410 firmwarebefore 2.20.0
- dell inspiron 14 5418 firmwarebefore 2.20.0
- dell inspiron 15 3511 firmwarebefore 1.23.0
- dell inspiron 15 5510 firmwarebefore 2.20.0
- dell inspiron 15 5518 firmwarebefore 2.20.0
- dell inspiron 24 5420 all-in-one firmwarebefore 1.4.0
- dell inspiron 24 5421 all-in-one firmwarebefore 1.4.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (dell). Independent of NVD's CPE analysis and usually ahead of it.
Dell CPG BIOS
- All versionsaffected
Same product
dell: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-32480
Dell BIOS contains an Improper Input Validation vulnerability.27Monitor
- CVE-2023-28075
Dell BIOS contain a Time-of-check Time-of-use vulnerability in BIOS.25Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
—
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
- CVE-2023-280750 days apart
Dell BIOS contain a Time-of-check Time-of-use vulnerability in BIOS.25Monitor
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Physical access to the device is required.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Physical
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-287 · Improper AuthenticationCVSS vector
CVSS:3.1/AV:P/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N
nvd-primary
Root cause
Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.
The bug in code
The whole CWE-287 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middleware
app.post("/admin-api/config", updateConfig);Fixed
const admin = express.Router();
admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);
app.use("/admin", admin);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Authentication AbuseCAPEC-114Medium
- Authentication BypassCAPEC-115Medium
- Identity SpoofingCAPEC-151likelihood: Medium · Medium
- Fake the Source of DataCAPEC-194Medium
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Utilizing REST's Trust in the System Resource to Obtain Sensitive DataCAPEC-57likelihood: Medium · Very High
- Session HijackingCAPEC-593likelihood: High · Very High
- Token ImpersonationCAPEC-633Medium
ATT&CK techniques
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.