dbcve.org
FedoraOperating system · Fedoraproject

CVE-2019-9433

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 information disclosure due to improper input validation. 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-80479354

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

In libvpx (a VP8/VP9 video codec library), there is an information disclosure vulnerability caused by improper input validation. This allows remote attackers to potentially disclose sensitive information through specially crafted video files without requiring additional execution privileges, but user interaction (such as opening a malicious video file) is required for exploitation.

MitigationApply the vendor-provided patch for libvpx to correct the input validation issue. Since this affects Android-10, ensure devices receive the appropriate system update. For products using libvpx directly, update to the patched version of the library.

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:= 8.0= 9.0= 10.0
Ubuntu LinuxOperating system
Affected:= 14.04= 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
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. Identify if libvpx library is installed
    Run 'dpkg -l | grep libvpx' (Debian/Ubuntu) or 'rpm -qa | grep libvpx' (Fedora/openSUSE) to list installed libvpx packages
    Affected if libvpx package is present on the system
  2. Determine installed libvpx version
    Run 'dpkg -l libvpx' or 'rpm -q libvpx' to retrieve the exact version number of the installed library
    Affected if The installed version matches or falls within the affected version ranges for your distribution (check against the CVE reference)
  3. Verify video processing capability
    Check if applications that use libvpx for VP8/VP9 decoding are present: run 'ldconfig -p | grep vpx' to see if the library is linked to any applications
    Affected if libvpx is actively linked and available to video playback applications
  4. Confirm operating system version
    Run 'cat /etc/os-release' or 'uname -r' to identify the exact OS version
    Affected if The system runs a distribution version listed as affected (Fedora 30/31, Debian 8/9/10, Ubuntu 14.04/16.04/18.04/19.04, openSUSE Leap 15.1, or Android 10)
  5. Check for Android-specific exposure
    On Android devices, verify the Android version under Settings > About Phone > Android version
    Affected if Device runs Android 10.0 and contains libvpx libraries in /system/lib or /vendor/lib

The system is affected if it runs one of the listed distribution versions AND has a vulnerable version of libvpx installed that processes VP8/VP9 video content.

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 vendor-provided patch for libvpx to correct the input validation issue. Since this affects Android-10, ensure devices receive the appropriate system update. For products using libvpx directly, update to the patched version of the library.

Fix this in Fedora Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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