CVE-2017-0431: An elevation of privilege vulnerability in Qualcomm closed source components

Recommended actionWithin 7 days

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

Patch available

What, why and how

An elevation of privilege vulnerability in Qualcomm closed source components. Product: Android. Versions: Android kernel. Android ID: A-32573899.

What

An elevation of privilege vulnerability in Qualcomm closed source components. Product: Android. Versions: Android kernel. Android ID: A-32573899.

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 with low privileges. If successful, the issue may gain additional privileges.

What

An elevation of privilege vulnerability in Qualcomm closed source components. Product: Android. Versions: Android kernel. Android ID: A-32573899.

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 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 → vulnerable operation → 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.: CWE not yet assigned
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 escalation

Official authority intelligence

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

ENISA EUVD · EUVD-2017-0785Official EUVD mapping

0 linked advisory records.

Official EUVD record ↗

Canadian Centre for Cyber Security · English · AV17-018Android security bulletin – February 2017

hrough remote code execution on affected devices using multiple methods such as email, web browsing, and MMS when processing media files. CVE References: CVE-2016-5552, CVE-2016-8414, CVE-2016-8418, CVE-2016-8480, CVE-2016-8481, CVE-2014-9914, CVE-2016-10044, CVE-2017-0405, CVE-2017-0406, CVE-2017-0407, CVE-2017-0408, CVE-2017-0409, CVE-2017-0410, CVE-2017-0411, CVE-2017-0412, CVE-2017-0413, CVE-2017-0414, CVE-2017-0415, CVE-2017-0416, CVE-2017-0417, CVE-2017-0418, CVE-2017-0419, CVE-2017-0420, CVE-2017-0421, CVE-2017-0422, CVE-2017-0423, CVE-2017-0424, CVE-2017-0425, CVE-2017-0426, CVE-2017-0427, CVE-2017-0428, CVE-2017-0429, CVE-2017-0430, CVE-2017-0431, CVE-2017-0432, CVE-2017-0433, CVE-2017-0434, CVE-2017-0435, CVE-2017-0436, CVE-2017-0437, CVE-2017-0438, CVE-2017-0439CVE-2017-0440, CVE-2017-0441, CVE-2017-0442, CVE-2017-0443, CVE-2017-0444, CVE-2017-0445, CVE-2017-0446, CVE-2017-0447, CVE-2017-0448, CVE-2017-0449, CVE-2017-0450, CVE-2017-0451. Suggested Action CCIRC recommends that system administrators look with their respected Android phone vendor and carrier when the update will be available and test and deploy the vendor-released updates to affected applications accordingly. References Android Security Bulletin: https://source.android.com/security/bulletin/2017-02-01.html

Official advisory ↗

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

.cve.org/CVERecord?id=CVE-2017-0422 Référence CVE CVE-2017-0423 https://www.cve.org/CVERecord?id=CVE-2017-0423 Référence CVE CVE-2017-0424 https://www.cve.org/CVERecord?id=CVE-2017-0424 Référence CVE CVE-2017-0425 https://www.cve.org/CVERecord?id=CVE-2017-0425 Référence CVE CVE-2017-0426 https://www.cve.org/CVERecord?id=CVE-2017-0426 Référence CVE CVE-2017-0427 https://www.cve.org/CVERecord?id=CVE-2017-0427 Référence CVE CVE-2017-0428 https://www.cve.org/CVERecord?id=CVE-2017-0428 Référence CVE CVE-2017-0429 https://www.cve.org/CVERecord?id=CVE-2017-0429 Référence CVE CVE-2017-0430 https://www.cve.org/CVERecord?id=CVE-2017-0430 Référence CVE CVE-2017-0431 https://www.cve.org/CVERecord?id=CVE-2017-0431 Référence CVE CVE-2017-0432 https://www.cve.org/CVERecord?id=CVE-2017-0432 Référence CVE CVE-2017-0433 https://www.cve.org/CVERecord?id=CVE-2017-0433 Référence CVE CVE-2017-0434 https://www.cve.org/CVERecord?id=CVE-2017-0434 Référence CVE CVE-2017-0435 https://www.cve.org/CVERecord?id=CVE-2017-0435 Référence CVE CVE-2017-0436 https://www.cve.org/CVERecord?id=CVE-2017-0436 Référence CVE CVE-2017-0437 https://www.cve.org/CVERecord?id=CVE-2017-0437 Référence CVE CVE-2017-0438 https://www.cve.org/CVERecord?id=CVE-2017-0438 Référence CVE CVE-2017-0439 https://www.cve.org/CVERecord?id=CVE-2017-0439 Ré

Official advisory ↗

JVN iPedia · Japanese · JVNDB-2017-012993Android の Qualcomm 製品における認可・権限・アクセス制御に関する脆弱性

Android の Qualcomm 製品には、認可・権限・アクセス制御に関する脆弱性が存在します。本脆弱性は、Android ID: A-32573899 として公開されています。

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: Android kernel
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 5 Apr 2018 · Last source change 16 Sept 2024, 22:24 UTC · CWE not yet assigned

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-0785

Product sourceCNA

Remediation sourceCVE/CNA references

CWE sourceUnavailable

NVD statusNVD modified after enrichment

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗

16 Sept 2024, 22:24 UTC
Vendor guidanceAuthoritative vendor guidance changed from no authoritative guidance recorded to authoritative remediation link · patch.
Before
no authoritative guidance recorded
After
authoritative remediation link · patch
af854a3a-2127-422b-91ae-364da2661108 ↗
16 Sept 2024, 22:24 UTC
Affected versionsThe structured affected or fixed version information changed.
Before
Android kernel · Fixed: No fixed version is explicitly recorded in the structured CVE data.
After
Android kernel · 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 ↗
16 Sept 2024, 22:24 UTC
Remediation statusRemediation status changed from Awaiting fix to Patch available.
Before
Awaiting fix
After
Patch available
af854a3a-2127-422b-91ae-364da2661108 ↗
16 Sept 2024, 22:24 UTC
SeveritySeverity changed from Unknown to High.
Before
Unknown
After
High
NIST NVD ↗
16 Sept 2024, 22:24 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 ↗
1 Sept 2026, 02:42 UTC
ENISA EUVD mappingEUVD-2017-0785 was added to the official ENISA EUVD mapping for this CVE.
Before
not recorded
After
{"euvdId":"EUVD-2017-0785"}
ENISA EUVD ↗
16 Sept 2024, 22:24 UTC
Catalogue recordCVE added to the BlackTree catalogue.
CNA ↗

2018-04-05CVE published

2024-09-16Fixed release or patch reference recorded

ENISA EUVD · EUVD-2017-0785↗Patch or update reference↗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.

An elevation of privilege vulnerability in Qualcomm closed source components

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-0785

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

What changed after publication

An elevation of privilege vulnerability in Qualcomm closed source components

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

EUVD-2017-0785

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.