CVE-2019-1253
Microsoft Windows 10 1709
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2019-1253 is a high-severity Link Following (CWE-59) vulnerability in Microsoft Windows 10 1709. Its CVSS base score is 7.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Path Interception (T1034); ranked in the top 4% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
An elevation of privilege vulnerability exists in the Windows AppX Deployment Server when it improperly handles junctions. The flaw, tracked as CVE-2019-1253, affects Windows systems and carries a CVSS 3.1 base score of 7.8. It is distinct from the related issues CVE-2019-1215, CVE-2019-1278, and CVE-2019-1303.
An attacker who has already obtained code execution on a victim system can exploit the weakness to escalate privileges. Successful exploitation grants the attacker full control over confidentiality, integrity, and availability on the affected host without requiring user interaction beyond the initial foothold.
Microsoft's security advisory and the CISA Known Exploited Vulnerabilities catalog address the issue, indicating that patches are available through standard Windows update channels. Public exploit code has been published, confirming that the vulnerability has been observed in real-world exploitation.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2019-9819
Vulnerability Data
An elevation of privilege vulnerability exists when the Windows AppX Deployment Server improperly handles junctions.To exploit this vulnerability, an attacker would first have to gain execution on the victim system, aka 'Windows Elevation of Privilege Vulnerability'. This CVE ID is…
more
unique from CVE-2019-1215, CVE-2019-1278, CVE-2019-1303.
- CWE(s)
- KEV Date Added
- 15 March 2022
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V15.4.2
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 require code to validate paths and avoid unsafe link following.
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 link-following flaws before release.
Secure SDLC practices can mandate link-resolution checks and canonicalization before file access.
Application security requirements can explicitly require safe handling of symbolic links and path traversal.
Secure architecture principles include input validation and safe file-access design patterns.
Secure coding standards directly address canonicalization and symlink attacks during implementation.
Access-control rules can limit which files are reachable, reducing exposure to malicious links.