dbcve.org
Ubuntu LinuxOperating system · Canonical

CVE-2019-9325

MEDIUM · 6.5 CVSS v3.1 Published 2019-09-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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
In libvpx, there is a possible out of bounds read due to a missing bounds check. 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-112001302

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 confidence

In libvpx (the VP8/VP9 video codec library used in Android), there is an out of bounds read vulnerability caused by a missing bounds check during video frame processing. This could allow remote information disclosure when a user opens a specially crafted video file, as the missing bounds check allows reading beyond allocated memory buffers.

MitigationApply the Android security patch for Android-10 (Android ID A-112001302) which addresses the libvpx vulnerability. Users should avoid opening untrusted video files from unknown sources until the patch is applied.

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
Ubuntu LinuxOperating system
Affected:= 16.04= 18.04= 19.04
FedoraOperating system
Affected:= 30= 31
Debian LinuxOperating system
Affected:= 9.0= 10.0
AndroidOperating system
Affected:= 10.0
LeapOperating system
Affected:= 15.1

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

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

  1. Check if libvpx library is installed
    On Ubuntu/Debian: dpkg -l | grep libvpx. On Fedora: rpm -qa | grep libvpx. On OpenSUSE: rpm -qa | grep libvpx
    Affected if libvpx package is not installed or no output returned means not affected
  2. Determine installed libvpx version
    Run: dpkg -l libvpx* (Ubuntu/Debian) or rpm -q libvpx (Fedora/OpenSUSE). Record the exact version number shown
    Affected if Version number cannot be determined or library not found means not affected
  3. Compare version against known vulnerable range
    Research libvpx version history: the vulnerability exists in versions prior to the fixed release. Check if your installed version predates mid-2019 security fixes. If running a version from 2018 or earlier, likely affected
    Affected if Installed version is older than mid-2019 releases or no patch has been applied
  4. Verify video processing capability
    Confirm the system can process VP8/VP9 video: check if libvpx is linked to video players (ffpeg, mplayer, etc.) using: ldd $(which ffmpeg 2>/dev/null) | grep vpx
    Affected if libvpx is loaded by video applications and could be triggered by malicious files
  5. Check system patch level for Android
    On Android 10 devices: Go to Settings > About Phone > Build Number. Verify if Android security patch level is dated after the CVE disclosure (2019)
    Affected if Security patch level is older than mid-2019 or build number predates the fix

Affected if libvpx is installed and its version predates the mid-2019 security updates that addressed CVE-2019-9325, or if Android 10 has not received the relevant security patch.

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 Android-10 (Android ID A-112001302) which addresses the libvpx vulnerability. Users should avoid opening untrusted video files from unknown sources until the patch is applied.

Fix this in Ubuntu Linux Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-2019-9325 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