CVE-2014-9878: n/a: security vulnerability

Recommended actionWithin 7 days

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

Patch available

What, why and how

drivers/mmc/card/mmc_block_test.c in the Qualcomm components in Android before 2016-08-05 on Nexus 5 devices does not reject kernel-space buffer addresses, which allows attackers to gain privileges via a crafted application, aka Android internal bug 28769208 and Qualcomm internal bug CR547479.

What

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

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 → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface: Local
Privileges required: None: unauthenticated exploitation is possible
User interaction: Required interaction required
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-264 ↗
CWE-264. Open the MITRE definition for the exact weakness description.
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:N/UI:R/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.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.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.

UnauthenticatedCWE-264

Official authority intelligence

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

ENISA EUVD · EUVD-2014-9683Official EUVD mapping

0 linked advisory records.

Official EUVD record ↗

Canadian Centre for Cyber Security · English · AV16-123Android security bulletin – August 2016

se of this advisory is to bring attention to the Android Security Bulletin for August. Assessment The Android Security Bulleting addresses a security update for 42 vulnerabilities (8 Critical, 21 High, 13 Moderate). The most critical ones, could potentially enable remote code execution on affected devices. This update is also distributed to the Android Open Source Project (AOSP) repository. CVE References: CVE-2012-6701, CVE-2014-9863, CVE-2014-9864, CVE-2014-9865, CVE-2014-9866, CVE-2014-9867, CVE-2014-9868, CVE-2014-9869, CVE-2014-9870, CVE-2014-9871, CVE-2014-9872, CVE-2014-9873, CVE-2014-9874, CVE-2014-9875, CVE-2014-9876, CVE-2014-9877, CVE-2014-9878, CVE-2014-9879, CVE-2014-9880, CVE-2014-9881, CVE-2014-9882, CVE-2014-9883, CVE-2014-9884, CVE-2014-9885, CVE-2014-9886, CVE-2014-9887, CVE-2014-9888, CVE-2014-9889, CVE-2014-9890, CVE-2014-9891, CVE-2014-9892, CVE-2014-9893, CVE-2014-9894, CVE-2014-9895, CVE-2014-9896, CVE-2014-9897, CVE-2014-9898, CVE-2014-9899, CVE-2014-9900, CVE-2014-9901, CVE-2014-9902, CVE-2014-9903, CVE-2014-9904, CVE-2015-1593, CVE-2015-2686, CVE-2015-8937, CVE-2015-8938, CVE-2015-8939, CVE-2015-8940, CVE-2015-8941, CVE-2015-8942, CVE-2015-8943, CVE-2015-8944, CVE-2016-2497, CVE-2016-2504, CVE-2016-2544, CVE-2016-2546, CVE-2016-2842, CVE-2016-3672, CVE-2016-3819, CVE

Official advisory ↗

CERT-FR · French · CERTFR-2016-AVI-257Multiples vulnérabilités dans Google Android (Nexus)

.cve.org/CVERecord?id=CVE-2014-9869 Référence CVE CVE-2014-9870 https://www.cve.org/CVERecord?id=CVE-2014-9870 Référence CVE CVE-2014-9871 https://www.cve.org/CVERecord?id=CVE-2014-9871 Référence CVE CVE-2014-9872 https://www.cve.org/CVERecord?id=CVE-2014-9872 Référence CVE CVE-2014-9873 https://www.cve.org/CVERecord?id=CVE-2014-9873 Référence CVE CVE-2014-9874 https://www.cve.org/CVERecord?id=CVE-2014-9874 Référence CVE CVE-2014-9875 https://www.cve.org/CVERecord?id=CVE-2014-9875 Référence CVE CVE-2014-9876 https://www.cve.org/CVERecord?id=CVE-2014-9876 Référence CVE CVE-2014-9877 https://www.cve.org/CVERecord?id=CVE-2014-9877 Référence CVE CVE-2014-9878 https://www.cve.org/CVERecord?id=CVE-2014-9878 Référence CVE CVE-2014-9879 https://www.cve.org/CVERecord?id=CVE-2014-9879 Référence CVE CVE-2014-9880 https://www.cve.org/CVERecord?id=CVE-2014-9880 Référence CVE CVE-2014-9881 https://www.cve.org/CVERecord?id=CVE-2014-9881 Référence CVE CVE-2014-9882 https://www.cve.org/CVERecord?id=CVE-2014-9882 Référence CVE CVE-2014-9883 https://www.cve.org/CVERecord?id=CVE-2014-9883 Référence CVE CVE-2014-9884 https://www.cve.org/CVERecord?id=CVE-2014-9884 Référence CVE CVE-2014-9885 https://www.cve.org/CVERecord?id=CVE-2014-9885 Référence CVE CVE-2014-9886 https://www.cve.org/CVERecord?id=CVE-2014-9886 Ré

Official advisory ↗

JVN iPedia · Japanese · JVNDB-2016-004222Nexus 5 デバイス上で稼動する Android の Qualcomm コンポーネントの drivers/mmc/card/mmc_block_test.c における権限を取得される脆弱性

Nexus 5 デバイス上で稼動する Android の Qualcomm コンポーネントの drivers/mmc/card/mmc_block_test.c は、カーネル空間のバッファのアドレスを拒否しないため、権限を取得される脆弱性が存在します。ベンダは、本脆弱性を Android internal bug 28769208 および Qualcomm internal bug CR547479 として公開しています。

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: n/a: n/a
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 Aug 2016 · Last source change 6 Aug 2024, 13:55 UTC · CWE-264

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-2014-9683

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 ↗

6 Aug 2024, 13:55 UTC
Vendor guidanceAuthoritative vendor guidance changed from no authoritative guidance recorded to authoritative remediation link · patch, vendor advisory.
Before
no authoritative guidance recorded
After
authoritative remediation link · patch, vendor advisory
af854a3a-2127-422b-91ae-364da2661108 ↗
6 Aug 2024, 13:55 UTC
Affected versionsThe structured affected or fixed version information changed.
Before
n/a · Fixed: No fixed version is explicitly recorded in the structured CVE data.
After
n/a · 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 ↗
6 Aug 2024, 13:55 UTC
Remediation statusRemediation status changed from Awaiting fix to Patch available.
Before
Awaiting fix
After
Patch available
af854a3a-2127-422b-91ae-364da2661108 ↗
6 Aug 2024, 13:55 UTC
SeveritySeverity changed from Unknown to High.
Before
Unknown
After
High
NIST NVD ↗
6 Aug 2024, 13:55 UTC
CVSS scoreCVSS score changed from not recorded to 7.8 (CVSS 3.0 · NIST NVD · CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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:N/UI:R/S:U/C:H/I:H/A:H)
NIST NVD ↗
1 Sept 2026, 02:42 UTC
ENISA EUVD mappingEUVD-2014-9683 was added to the official ENISA EUVD mapping for this CVE.
Before
not recorded
After
{"euvdId":"EUVD-2014-9683"}
ENISA EUVD ↗
6 Aug 2024, 13:55 UTC
Catalogue recordCVE added to the BlackTree catalogue.
CNA ↗

2016-08-06CVE published

2024-08-06Fixed release or patch reference recorded

ENISA EUVD · EUVD-2014-9683↗CVE authority or vendor reference↗Patch or update 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.

n/a: security vulnerability

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-2014-9683

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

What changed after publication

n/a: security vulnerability

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

EUVD-2014-9683

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

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