CVE-2024-52537: Dell Client Platform Firmware Update Utility contains an Improper Link Resolution vulnerability.
Noroxi assessment
Priority: Monitor (action score 26/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.17% (FIRST EPSS).
- Someone with local access to the system can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Dell Dell Client Platform BIOS 1.00.23,1.00.28, 1.00.44, 1.00.28.
Low priority for now. Upgrade to Dell Dell Client Platform BIOS 1.00.23,1.00.28, 1.00.44, 1.00.28 or later.
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 Client Platform Firmware Update Utility contains an Improper Link Resolution vulnerability. A high privileged attacker with local access could potentially exploit this vulnerability, leading to Elevation of Privileges.
- Published
- Dec 11, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- CWE-61
Report tools
Action score
26
Low priority for now.
- CVSS
- 26 / 40 · 6.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 6.7
- CNA · dell
- 6.3
- 0.4 point gap
CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H
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
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi 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 | dock hd22q firmware update utility | cpe:2.3:a:dell:dock_hd22q_firmware_update_utility |
| dell | dock wd19 firmware update utility | cpe:2.3:a:dell:dock_wd19_firmware_update_utility |
| dell | dock wd22tb4 firmware update utility | cpe:2.3:a:dell:dock_wd22tb4_firmware_update_utility |
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| microsoft | windows | cpe:2.3:o:microsoft:windows |
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 Dell Client Platform BIOS
- N/A and later · before 1.00.44, 1.00.28affected · semver
- N/A and later · before 1.00.23,1.00.28affected · semver
Affected versions · NVD (6)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- dell dock hd22q firmware update utilitybefore 1.00.23
- dell dock hd22q firmware update utilitybefore 1.00.28
- dell dock wd19 firmware update utilitybefore 01.00.44
- dell dock wd19 firmware update utilitybefore 01.00.28
- dell dock wd22tb4 firmware update utilitybefore 01.00.28
- dell dock wd22tb4 firmware update utilitybefore 01.00.44
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Dell Dell Client Platform BIOS | 1.00.23,1.00.28 | Vendor (CNA) |
| Dell Dell Client Platform BIOS | 1.00.44, 1.00.28 | Vendor (CNA) |
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.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Sandro Poppifinder
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-61 · UNIX Symbolic Link (Symlink) FollowingCVSS vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
nvd-primary
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)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.