Menu

Star on GitHub · 3.2k

CVE-2017-6262

7.0 · HIGH

NVIDIA driver contains a vulnerability where it is possible a use after free malfunction can occur due to a race condition which could enable unauthorized code execution and possibly lead to elevat…

Published Dec 6, 2017CWE-416EPSS 0.16%

Overview

CVE-2017-6262 is a high-severity vulnerability. It was published on December 6, 2017 and has a CVSS 3.0 base score of 7.0 (HIGH).

This vulnerability has a CVSS 3.0 base score of 7.0, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

NVIDIA driver contains a vulnerability where it is possible a use after free malfunction can occur due to a race condition which could enable unauthorized code execution and possibly lead to elevation of privileges. This issue is rated as high. Product: Android. Version: N/A. Android ID: A-38045794. References: N-CVE-2017-6262.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2017-6262?

CVE-2017-6262 is a high-severity vulnerability. It was published on December 6, 2017 and has a CVSS 3.0 base score of 7.0 (HIGH).

How severe is CVE-2017-6262?

This vulnerability has a CVSS 3.0 base score of 7.0, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2017-6262?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2017-6262?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2017-6262 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2017

View all