dbcve.org
FedoraOperating system · Fedoraproject

CVE-2019-9371

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 resource exhaustion due to improper input validation. This could lead to remote denial of service with no additional execution privileges needed. User interaction is needed for exploitation. Product: AndroidVersions: Android-10Android ID: A-132783254

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 by Android), improper input validation allows remote attackers to cause resource exhaustion, leading to denial of service. Exploitation requires user interaction, likely through the victim opening a specially crafted video file.

MitigationApply Android security patches for Android-10 that address this vulnerability in libvpx; consider disabling or restricting video playback from untrusted 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
FedoraOperating system
Affected:= 30= 31
Debian LinuxOperating system
Affected:= 9.0= 10.0
Ubuntu LinuxOperating system
Affected:= 16.04= 18.04= 19.04
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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 checks

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

  1. Confirm libvpx library presence
    Search for the libvpx shared library on the system. On Linux distributions, run: find /usr -name 'libvpx*' 2>/dev/null. On Android, check /system/lib or /system/lib64 for libvpx.so files.
    Affected if The libvpx library file exists on the system
  2. Identify installed libvpx version
    Run 'rpm -q libvpx' on Fedora/OpenSUSE, 'dpkg -l | grep libvpx' on Debian/Ubuntu, or check the library file details using 'ls -la /path/to/libvpx.so'. Extract version info from package metadata or library file properties.
    Affected if The installed package version matches the affected distribution versions (Fedora 30/31, Debian 9.0/10.0, Ubuntu 16.04/18.04/19.04, OpenSUSE Leap 15.1)
  3. Check for video processing applications
    Identify applications that use libvpx for video decoding. Common tools include FFmpeg (ffmpeg -codecs | grep vp9), VLC, web browsers, or video players. Run 'ldd /path/to/application | grep vpx' to confirm linkage.
    Affected if Applications capable of processing video files are installed and linked against the vulnerable libvpx library
  4. Verify Android version if applicable
    On Android devices, check the Android version in Settings > About Phone > Android version. The vulnerability affects Android 10.0 specifically.
    Affected if The device runs Android 10.0 and contains the vulnerable libvpx library

A system is affected if it runs one of the listed distribution versions with libvpx installed and has applications that can process untrusted video files using that library.

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 Android security patches for Android-10 that address this vulnerability in libvpx; consider disabling or restricting video playback from untrusted sources until the patch is applied.

Fix this in Fedora Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-9371 — 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-9371 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