Security readout for executives and security teams
Plain-English summary
A logged-in attacker with limited Windows privileges can abuse AppX Deployment Service hard-link handling to gain greater control of an affected computer. It is not a direct remote-entry flaw, but it can turn an initial foothold into severe system compromise without user interaction.
Executive priority
Treat remediation as urgent, especially on servers, shared endpoints, and systems accessible to lower-privileged users. Known exploitation materially increases urgency, while the local attack requirement means priority should remain risk-based rather than implying direct internet exploitation.
Technical view
CVE-2019-1130 is a Windows AppXSVC elevation-of-privilege vulnerability caused by improper hard-link handling (CWE-59). It has CVSS 3.1 score 7.8: local access and low privileges are required, complexity is low, no user interaction is needed, and confidentiality, integrity, and availability impacts are high. It is distinct from CVE-2019-1129.
Likely exposure
Exposure includes the listed Windows 8.1, RT 8.1, Windows 10, and Windows Server releases where Microsoft’s remediation is absent. Endpoints, shared systems, and servers allowing local or interactive access deserve priority. The vulnerability alone does not provide remote initial access.
Exploitation context
CISA’s Known Exploited Vulnerabilities designation confirms exploitation in the wild. The supplied evidence does not identify campaigns, attackers, exploitation frequency, public exploit availability, or indicators of compromise. Treat it primarily as a post-compromise privilege-escalation risk.
Researcher notes
Focus validation on AppXSVC hard-link handling and privilege boundaries without assuming an undocumented exploit path. The CVSS vector is AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. The record explicitly distinguishes this issue from CVE-2019-1129. The supplied bundle provides no exploit mechanics, indicators, campaign attribution, or exact update identifiers.
Mitigation direction
- Consult Microsoft’s CVE advisory and apply the applicable vendor security update.
- Prioritize affected systems because CISA lists the vulnerability as known exploited.
- Use CISA’s catalog entry to establish remediation urgency and track completion.
- Escalate unsupported or unpatchable systems for compensating controls based on vendor guidance.
Validation and detection
- Inventory systems against every affected Windows and Windows Server release listed.
- Verify installed update or build status against Microsoft’s CVE advisory.
- Confirm vulnerability-management records recognize CVE-2019-1130 as CISA KEV.
- Review relevant endpoint telemetry for unexplained privilege elevation involving AppXSVC.
- Do not infer safety from missing public indicators in the supplied evidence.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-59: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2019-1130 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- Yes
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CISA KEV status
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- Added to KEVCISA-ADP
CISA Known Exploited Vulnerabilities metadata lists this CVE as known exploited.
- ADP timelineCISA-ADP
CVE-2019-1130 added to CISA KEV
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2022-05-23T00:00:00.000Z: CVE-2019-1130 added to CISA KEV
Source materials
- CVE List V5 sourceCVE List V5
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1130CVE reference, microsoft · x_refsource_MISC
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2019-1130CVE reference, CISA-ADP · government-resource
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Link Resolution Before File Access ('Link Following')
Improper Link Resolution Before File Access ('Link Following') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.