CVE-2023-32454
Dell Update Package Framework ≤ 4.9.4.36
Raw vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:HSummary
CVE-2023-32454 is a medium-severity Insecure Operation on Windows Junction / Mount Point (CWE-1386) vulnerability in Dell Update Package Framework. Its CVSS base score is 6.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Path Interception (T1034); ranked at the 6th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-36698
Vulnerability Data
DUP framework version 4.9.4.36 and prior contains insecure operation on Windows junction/Mount point vulnerability. A local malicious standard user could exploit the vulnerability to create arbitrary files, leading to denial of service
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.3.3V15.4.2
Mitigating Controls (NIST 800-53 r5) AI
Proper enforcement of access authorizations on the resolved target resource stops a link from reaching an unintended object.
Information-flow rules that validate the final target of a name prevent unintended data access through mount points or junctions.
Least-privilege limits the damage an attacker can cause after following an unintended link.
Validating file-name inputs can reject or canonicalize names that resolve to links before access occurs.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prevent improper junction/mount-point handling during design and coding.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect junction/mount-point weaknesses before release.
Secure development lifecycle can mandate junction/mount-point validation during design and coding.
Application security requirements can explicitly require protection against Windows reparse-point attacks.
Secure system architecture principles include canonicalization and path-traversal defenses that mitigate junction attacks.
Secure coding standards directly address safe file/directory handling to prevent insecure junction operations.
Information access restriction reduces exposure but does not prevent the technical flaw itself.