BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2017
CVE-2015-9032High confidence

In all Android releases from CAF using the Linux kernel, a DRM key was exposed to QTEE applications

Qualcomm, Inc. · All Qualcomm products

3.3LowCVSS 3.0
Recommended action
Scheduled

Low technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Fix not verified
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityLowOperational priority:Low, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.46% for the current model date.

Compensating controls

  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Qualcomm, Inc. All Qualcomm products and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: No default targetRemediation target: Normal maintenance

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Optional official sources

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

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2015-8886

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Low technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Fix not verified
01

What, why and how

In all Android releases from CAF using the Linux kernel, a DRM key was exposed to QTEE applications.

What

In all Android releases from CAF using the Linux kernel, a DRM key was exposed to QTEE applications.

Why

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

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

In all Android releases from CAF using the Linux kernel, a DRM key was exposed to QTEE applications.

Why

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

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.

02

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 → Exposure of Sensitive Information to an Unauthorized Actor → 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-200 ↗

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

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:L/I:N/A:N

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.CLowConfidentiality impact: A successful attack can cause a limited loss.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.
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-200
A

Official authority intelligence

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

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

.cve.org/CVERecord?id=CVE-2015-9023 Référence CVE CVE-2015-9024 https://www.cve.org/CVERecord?id=CVE-2015-9024 Référence CVE CVE-2015-9025 https://www.cve.org/CVERecord?id=CVE-2015-9025 Référence CVE CVE-2015-9026 https://www.cve.org/CVERecord?id=CVE-2015-9026 Référence CVE CVE-2015-9027 https://www.cve.org/CVERecord?id=CVE-2015-9027 Référence CVE CVE-2015-9028 https://www.cve.org/CVERecord?id=CVE-2015-9028 Référence CVE CVE-2015-9029 https://www.cve.org/CVERecord?id=CVE-2015-9029 Référence CVE CVE-2015-9030 https://www.cve.org/CVERecord?id=CVE-2015-9030 Référence CVE CVE-2015-9031 https://www.cve.org/CVERecord?id=CVE-2015-9031 Référence CVE CVE-2015-9032 https://www.cve.org/CVERecord?id=CVE-2015-9032 Référence CVE CVE-2015-9033 https://www.cve.org/CVERecord?id=CVE-2015-9033 Référence CVE CVE-2016-1029 https://www.cve.org/CVERecord?id=CVE-2016-1029 Référence CVE CVE-2016-1033 https://www.cve.org/CVERecord?id=CVE-2016-1033 Référence CVE CVE-2016-1034 https://www.cve.org/CVERecord?id=CVE-2016-1034 Référence CVE CVE-2016-1839 https://www.cve.org/CVERecord?id=CVE-2016-1839 Référence CVE CVE-2016-4658 https://www.cve.org/CVERecord?id=CVE-2016-4658 Référence CVE CVE-2016-5131 https://www.cve.org/CVERecord?id=CVE-2016-5131 Référence CVE CVE-2016-5861 https://www.cve.org/CVERecord?id=CVE-2016-5861 Ré

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2017-004786Linux Kernel を使用している CAF リリースの Android における情報漏えいに関する脆弱性

Linux Kernel を使用している CAF リリースの Android には、情報漏えいに関する脆弱性が存在します。

Official advisory ↗
03

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.
Fix not verified
Affected
All Qualcomm products: All Android releases from CAF using the Linux kernel
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 13 Jun 2017 · Last source change 6 Aug 2024, 08:36 UTC · CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor

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-2015-8886
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. ENISA EUVD mappingEUVD-2015-8886 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2015-8886"}
    ENISA EUVD ↗
  2. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: source.android.com/2017-06-01.
    Before
    no authoritative guidance recorded
    After
    vendor advisory: source.android.com/2017-06-01
    source.android.com ↗
  3. SeveritySeverity changed from Unknown to Low.
    Before
    Unknown
    After
    Low
    NIST NVD ↗
  4. CVSS scoreCVSS score changed from not recorded to 3.3 (CVSS 3.0 · NIST NVD · CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N).
    Before
    not recorded
    After
    3.3 (CVSS 3.0 · NIST NVD · CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N)
    NIST NVD ↗
  5. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
ENISA EUVD · EUVD-2015-8886↗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.
Free version - for non-commercial use only.CVE-2015-9032 · cve.blacktree.nl