AndroidOperating system · Google

CVE-2017-13239

HIGH · 7.5 CVSS v3.0 Published 2018-02-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A information disclosure vulnerability in the Android framework (ui framework). Product: Android. Versions: 8.0. ID: A-66244132.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

An information disclosure vulnerability in the Android UI framework (android.view package) that allows unauthorized access to sensitive UI-related data or state information. The vulnerability exists in Android 8.0 and could enable a local or remote attacker to obtain information that should be protected.

MitigationApply the Android security patch for October 2017 (or subsequent patches addressing A-66244132) to Android 8.0 devices. For enterprise deployments, enforce patch management policies to ensure timely updates.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AndroidOperating system
Affected:= 8.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Android version is 8.0
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell
    Affected if Android version shows exactly 8.0 (oreo) - note that versions before or after 8.0 are not affected by this specific CVE)
  2. Confirm the android.view system component is present
    Check that /system/framework/framework.jar exists and contains android.view classes - or verify via 'pm list packages android.view'
    Affected if The android.view package is present and the device is running Android 8.0 (this is the default state for any Android 8.0 device)
  3. Check October 2017 security patch level
    Go to Settings > About Phone > Security patch level, or run 'getprop ro.build.version.security_patch' via ADB shell
    Affected if Security patch level is earlier than October 2017 or the patch level cannot be determined - the vulnerability exists in unpatched Android 8.0 devices

A device is affected if it is running Android 8.0 (exactly version 8.0) and has not received the October 2017 security patch or later patches addressing A-66244132.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Android security patch for October 2017 (or subsequent patches addressing A-66244132) to Android 8.0 devices. For enterprise deployments, enforce patch management policies to ensure timely updates.

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-13239 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-13239 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data