CVE-2019-9406
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 · uneditedIn libhevc there is a possible information disclosure due to uninitialized data. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is needed for exploitation. Product: AndroidVersions: Android-10Android ID: A-112552517
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 · high confidenceIn libhevc (Android's HEVC/H.265 video decoder), uninitialized data is being read and could be disclosed to an attacker. This memory disclosure vulnerability occurs when the library processes media content without properly initializing certain data structures, potentially exposing sensitive heap or stack memory contents.
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= 10.0CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Android version is 10.0Check the device system version: go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if The Android version is exactly 10.0 (not 9.x, 11.x, or later)
-
Confirm libhevc library is presentCheck for the library file on the device: run 'ls -la /system/lib64/libhevc.so' or 'ls -la /system/lib/libhevc.so' via ADB shellAffected if The libhevc.so library file exists on the device in /system/lib or /system/lib64
-
Check HEVC/H.265 video playback capabilityVerify the device supports HEVC/H.265 decoding: check for hevc in media codec lists via 'adb shell media codecs | grep -i hevc' or test with a HEVC video fileAffected if The device can decode HEVC/H.265 media content using libhevc
-
Determine libhevc library versionIf available, inspect the library version string: run 'adb shell dumpsys package com.android.internal.app.libhevc' or check file metadata with 'ls -la' on the libhevc.so fileAffected if The library version cannot be determined or matches the vulnerable Android 10.0 release build
The device is affected if it is running Android version 10.0 and uses the libhevc library for HEVC/H.265 video decoding, as the uninitialized data flaw exists in that specific Android release.
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.
From vendor dataApply the Android security patch for Android-10 that addresses the libhevc uninitialized data issue. Users should ensure their devices receive the latest Android system updates containing the CVE-2019-9406 fix.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-9406 — 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-2019-9406 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