CVE-2017-0807
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 · uneditedAn elevation of privilege vulnerability in the Android framework (ui framework). Product: Android. Versions: 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2. Android ID: A-35056974.
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 confidenceThis is an elevation of privilege vulnerability in the Android UI framework that allows a malicious application to potentially gain elevated access beyond its intended permissions. The flaw exists in the UI system component and affects Android versions 4.4.4 through 7.1.2.
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= 4.4.4= 5.0.2= 5.1.1= 6.0= 6.0.1= 7.0= 7.1.1= 7.1.2CVSS 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
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Check Android versionOpen Settings > About Phone > Android version, or run `getprop ro.build.version.release` in ADB shellAffected if Version is 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, or 7.1.2
-
Verify security patch levelOpen Settings > About Phone > Security patch level, or run `getprop ro.build.version.security_patch` in ADB shellAffected if Patch level is blank, empty, or shows a date earlier than March 2017 (2017-03)
-
Confirm UI framework is accessibleVerify the device is functional and UI framework is operational by checking if Settings and standard UI components load normallyAffected if Device is functional and runs an affected Android version listed above without the 2017-03 or later security patch
The device is affected if it runs Android 4.4.4 through 7.1.2 and has a security patch level earlier than March 2017.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedApply the relevant Android security patch level (2017-03 or later) from Google/device OEMs. For end-of-life devices no longer receiving updates, consider replacement with supported devices or implement additional mobile device management controls.
Android 8.0 (Oreo) or later, or apply the March 2017 Android Security Update that includes the fix for A-35056974
- 1. Back up all important data from the Android device to a secure location
- 2. Check if your device manufacturer has released a security update that includes the fix for Android ID A-35056974
- 3. If a manufacturer update is available, install it via Settings > System > Security & privacy > System updates or similar path
- 4. If no manufacturer update is available, consider upgrading to a newer Android version (Android 7.1.2 or later) that includes the security patch
- 5. Verify the security patch level by going to Settings > System > About phone > Security patch level
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-0807 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-0807 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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