Advisory [CVE-2019-1129 +1] Windows Server: elevation of privilege vulnerability exists when Windows AppX Deployment Service (AppXSVC) improperly handles hard links, aka 'Windows Elevation of Privilege Vulnerability'
This security Microsoft Server advisory covers CVE-2019-1130 and CVE-2019-1129 affecting Windows Server, version 1903 (Server Core installation).
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations. This bulletin covers 2 CVEs; its score, affected versions and guidance may apply to different issues within that bulletin.
VulniPulse record published
Android app · Google Play
Monitor future Microsoft Server CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
An elevation of privilege vulnerability exists when Windows AppX Deployment Service (AppXSVC) improperly handles hard links, aka 'Windows Elevation of Privilege Vulnerability'. This CVE ID is unique from CVE-2019-1129.
Affected products named by the advisory: Windows Server; Windows Server, version 1903 (Server Core installation).
CISA Known Exploited Vulnerability
- Listed:
- Mar 15, 2022 · federal remediation due Apr 5, 2022
- Required action:
- Apply updates per vendor instructions.
- Ransomware use:
- Known
KEV is a prioritization signal from CISA — remediation detail still comes from the vendor advisory.
- Windows Server 2012
- Windows Server 2012 (Core installation)
- Windows Server 2012 R2
- Windows Server 2012 R2 (Core installation)
- Windows Server 2016
- Windows Server 2016 (Core installation)
- Windows Server version 1803 (Core Installation)
- Windows Server 2019
- Windows Server 2019 (Core installation)
- Windows 8.1 for x64-based systems
- Windows RT 8.1
- Windows 10 for 32-bit Systems
Official advisory · medium-confidence parse· fetched 2 months ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · medium-confidence parse· fetched 2 months ago·verify at source
Mitigation
The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.
Official advisory · medium-confidence parse· fetched 2 months ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.