An information disclosure vulnerability exists when DirectX improperly handles objects in memory, aka 'DirectX Information Disclosure Vulnerability'.
CVE-2019-1216
MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence
This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 1.7% (76th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1.7%CVSS: 5.5Exploit: None knownExposed services: —
A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).
Internet exposure
The internet-exposure footprint is temporarily unavailable — the KEV-Exposure radar's record for this CVE could not be loaded just now. That is not a finding of zero exposed services; please retry shortly.
- CVSS v3
- 5.5
- EG Score
- 5.5MEDIUMmedium confidence
- EG Risk
- 30EG Risk 30/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity55% × 45%Exploitation2% × 40%Automatability30% × 15%CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation. - EPSS PROB
- 1.7%
- EPSS %ILE
- 76th
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).
A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
September 11, 2019
Last Modified
November 21, 2024
Advisory Details (1)
{"basis": {"same_cwe": "ok", "same_vendor": "no_siblings", "same_product": "no_data"}, "same_cwe": [{"cve_id": "CVE-2019-1219", "join_key": "CWE-200", "severity": "MEDIUM", "published": "2019-09-11T22:15:14.773Z", "kev_listed": false, "cvss_v3_score": 5.5, "epss_percentile": 0.76387, "echelongraph_score": 5.5, "echelongraph_severity": "MEDIUM"}, {"cve_id": "CVE-2019-1209", "join_key": "CWE-200", "severity": "MEDIUM", "published": "2019-09-11T22:15:14.46Z", "kev_listed": false, "cvss_v3_score": 6.5, "epss_percentile": 0.9331, "echelongraph_score": 6.5, "echelongraph_severity": "MEDIUM"}, {"cve_id": "CVE-2019-1244", "join_key": "CWE-200", "severity": "MEDIUM", "published": "2019-09-11T22:15:15.727Z", "kev_listed": false, "cvss_v3_score": 6.5, "epss_percentile": 0.96035, "echelongraph_score": 6.5, "echelongraph_severity": "MEDIUM"}, {"cve_id": "CVE-2019-1245", "join_key": "CWE-200", "severity": "MEDIUM", "published": "2019-09-11T22:15:15.803Z", "kev_listed": false, "cvss_v3_score": 6.5, "epss_percentile": 0.96198, "echelongraph_score": 6.5, "echelongraph_severity": "MEDIUM"}, {"cve_id": "CVE-2019-1251", "join_key": "CWE-200", "severity": "MEDIUM", "published": "2019-09-11T22:15:16.197Z", "kev_listed": false, "cvss_v3_score": 5.5, "epss_percentile": 0.76388, "echelongraph_score": 5.5, "echelongraph_severity": "MEDIUM"}, {"cve_id": "CVE-2019-1252", "join_key": "CWE-200", "severity": "MEDIUM", "published": "2019-09-11T22:15:16.273Z", "kev_listed": false, "cvss_v3_score": 6.5, "epss_percentile": 0.9912, "echelongraph_score": 7.9, "echelongraph_severity": "HIGH"}, {"cve_id": "CVE-2019-1263", "join_key": "CWE-200", "severity": "MEDIUM", "published": "2019-09-11T22:15:16.837Z", "kev_listed": false, "cvss_v3_score": 5.5, "epss_percentile": 0.94474, "echelongraph_score": 5.5, "echelongraph_severity": "MEDIUM"}, {"cve_id": "CVE-2019-1283", "join_key": "CWE-200", "severity": "MEDIUM", "published": "2019-09-11T22:15:17.93Z", "kev_listed": false, "cvss_v3_score": 5.5, "epss_percentile": 0.75227, "echelongraph_score": 5.5, "echelongraph_severity": "MEDIUM"}, {"cve_id": "CVE-2019-1286", "join_key": "CWE-200", "severity": "MEDIUM", "published": "2019-09-11T22:15:18.133Z", "kev_listed": false, "cvss_v3_score": 6.5, "epss_percentile": 0.92901, "echelongraph_score": 6.5, "echelongraph_severity": "MEDIUM"}, {"cve_id": "CVE-2019-1293", "join_key": "CWE-200", "severity": "MEDIUM", "published": "2019-09-11T22:15:18.523Z", "kev_listed": false, "cvss_v3_score": 5.5, "epss_percentile": 0.80684, "echelongraph_score": 5.5, "echelongraph_severity": "MEDIUM"}], "same_vendor": [], "same_product": []}.
5.5
MEDIUM
2019-09-11 22:15:14.647+00
Affected: [{"url": "https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1216", "tags": ["Patch", "Vendor Advisory"], "source": "[email protected]"}, {"url": "https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1216", "tags": ["Patch", "Vendor Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}]
An information disclosure vulnerability exists when DirectX improperly handles objects in memory, aka 'DirectX Information Disclosure Vulnerability'.Vendor Advisories for CVE-2019-1216(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Publicly available exploits
(1 reference)Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- msrcCVE-2019-1216First seen Sep 10, 2019
DirectX Information Disclosure Vulnerability
Open source ↗
Related CVEs
Related CVEs are temporarily unavailable — the same-product, same-vendor and same-CWE lists could not be loaded just now. That is not a sign that none exist; please retry shortly.
Frequently asked(5)
What is CVE-2019-1216?
CVE-2019-1216 is a medium vulnerability published on September 11, 2019. An information disclosure vulnerability exists when DirectX improperly handles objects in memory, aka 'DirectX Information Disclosure Vulnerability'.
When was CVE-2019-1216 disclosed?
CVE-2019-1216 was first published on September 11, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-1216 actively exploited?
CVE-2019-1216 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.7% probability of exploitation in the next 30 days (76th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2019-1216?
CVE-2019-1216 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2019-1216?
A fix for CVE-2019-1216 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2019-1216 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2019-1216
Is Your Infrastructure Affected by CVE-2019-1216?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.