CVE-2017-6279: Nvidia Corporation Android: Out-of-bounds Write

Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available

What, why and how

NVIDIA libnvmmlite_audio.so contains an elevation of privilege vulnerability when running in media server which may cause an out of bounds write and could lead to local code execution in a privileged process. This issue is rated as high. Product: Android. Version: N/A. Android: A-65023166. Reference: N-CVE-2017-6279.

What

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may gain additional privileges.

What

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may gain additional privileges.

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path: local access → Out-of-bounds Write → gain additional privileges
Attack surface: Local
Privileges required: Low: a basic authenticated account is required
User interaction: None
Attack complexity: Low: no specialised conditions are recorded
Security boundary: Unchanged: impact remains within the vulnerable component's security authority
Weakness ? CWE means Common Weakness Enumeration: a standard category for the underlying weakness.: CWE-787 ↗
CWE-787: Out-of-bounds Write. The product writes data past the end, or before the beginning, of the intended buffer.
CVSS vector ? CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Common Vulnerability Scoring System 3.0: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land: The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.

Privilege escalationCWE-787

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2017-15340Official EUVD mapping

0 linked advisory records.

Official EUVD record ↗

CERT-FR · French · CERTFR-2018-AVI-067Multiples vulnérabilités dans Google Android

ord?id=CVE-2017-15829 Référence CVE CVE-2017-17760 https://www.cve.org/CVERecord?id=CVE-2017-17760 Référence CVE CVE-2017-17761 https://www.cve.org/CVERecord?id=CVE-2017-17761 Référence CVE CVE-2017-17762 https://www.cve.org/CVERecord?id=CVE-2017-17762 Référence CVE CVE-2017-17764 https://www.cve.org/CVERecord?id=CVE-2017-17764 Référence CVE CVE-2017-17765 https://www.cve.org/CVERecord?id=CVE-2017-17765 Référence CVE CVE-2017-17767 https://www.cve.org/CVERecord?id=CVE-2017-17767 Référence CVE CVE-2017-17770 https://www.cve.org/CVERecord?id=CVE-2017-17770 Référence CVE CVE-2017-6258 https://www.cve.org/CVERecord?id=CVE-2017-6258 Référence CVE CVE-2017-6279 https://www.cve.org/CVERecord?id=CVE-2017-6279 Gestion détaillée du document le 06 février 2018 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

Official advisory ↗

JVN iPedia · Japanese · JVNDB-2017-012500Android における境界外書き込みに関する脆弱性

Android には、境界外書き込みに関する脆弱性が存在します。本脆弱性は、Android ID: A-65023166 および NVIDIA N-CVE-2017-6279 として公開されています。

Official advisory ↗

Patch and workaround

Operational remediation based on structured source evidence.

Status ? Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.: Patch available
Affected: Android: NA
Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action: Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround: No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.

Evidence and provenance

Published 6 Feb 2018 · Last source change 17 Sept 2024, 01:35 UTC · CWE-787 · Out-of-bounds Write

CVE recordCVE.org · 5.1

CVSS sourceNIST NVD

EPSS source

The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.

FIRST · tracked since 2026-09-01

European sourceENISA EUVD · EUVD-2017-15340

Product sourceCNA

Remediation sourceCVE/CNA references

CWE sourceNIST NVD

NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

1 Sep 2026, 02:42 UTC
ENISA EUVD mappingEUVD-2017-15340 was added to the official ENISA EUVD mapping for this CVE.
Before
not recorded
After
{"euvdId":"EUVD-2017-15340"}
ENISA EUVD ↗
17 Sep 2024, 01:35 UTC
Vendor guidanceAuthoritative vendor guidance changed: added patch: source.android.com/2018-02-01; added remediation: source.android.com/2018-02-01.
Before
no authoritative guidance recorded
After
patch: source.android.com/2018-02-01 · remediation: source.android.com/2018-02-01
source.android.com ↗
17 Sep 2024, 01:35 UTC
Affected versionsThe structured affected or fixed version information changed.
Before
NA · Fixed: No fixed version is explicitly recorded in the structured CVE data.
After
NA · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
CNA ↗
17 Sep 2024, 01:35 UTC
Remediation statusRemediation status changed from Awaiting fix to Patch available.
Before
Awaiting fix
After
Patch available
source.android.com ↗
17 Sep 2024, 01:35 UTC
SeveritySeverity changed from Unknown to High.
Before
Unknown
After
High
NIST NVD ↗
17 Sep 2024, 01:35 UTC
CVSS scoreCVSS score changed from not recorded to 7.8 (CVSS 3.0 · NIST NVD · CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).
Before
not recorded
After
7.8 (CVSS 3.0 · NIST NVD · CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H)
NIST NVD ↗
17 Sep 2024, 01:35 UTC
Catalogue recordCVE added to the BlackTree catalogue.
CNA ↗

2018-02-06CVE published

2024-09-17Fixed release or patch reference recorded

ENISA EUVD · EUVD-2017-15340↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗

Technical terms and abbreviations used in this report

CVE: Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS: Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS: Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE: Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA: CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP: Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD: National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT: A computer security incident response team that publishes warnings or coordinates incident response.
PoC: Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF: Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL: Living off the land: abuse of legitimate tools or system functions during an attack.

Nvidia Corporation Android: Out-of-bounds Write

Published severity in operational context

Evidence used

Compensating controls

Verification

National CERT insights
?
CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

ENISA European Vulnerability Database

EUVD-2017-15340