CVE-2017-0869

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2022-05-14. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

NVIDIA driver contains an integer overflow vulnerability which could cause a use after free and possibly lead to an elevation of privilege enabling code execution as a privileged process. This issue is rated as high. Version: N/A. Android ID: A-37776156. References: N-CVE-2017-0869.

CVSS v3
7.8
EG Score
7.8(medium)
EPSS
9.3%
KEV
Not listed

Published

January 12, 2018

Last Modified

November 21, 2024

Frequently asked(5)

What is CVE-2017-0869?
CVE-2017-0869 is a high vulnerability published on January 12, 2018. NVIDIA driver contains an integer overflow vulnerability which could cause a use after free and possibly lead to an elevation of privilege enabling code execution as a privileged process. This issue is rated as high. Version: N/A. Android ID: A-37776156. References: N-CVE-2017-0869.
When was CVE-2017-0869 disclosed?
CVE-2017-0869 was first published in the National Vulnerability Database on January 12, 2018, 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-2017-0869 actively exploited?
CVE-2017-0869 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 9.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-0869?
CVE-2017-0869 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2017-0869?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-0869, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2017-0869

Explore →

Is Your Infrastructure Affected by CVE-2017-0869?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.