dbcve.org
FedoraOperating system · Fedoraproject

CVE-2019-2126

HIGH · 8.8 CVSS v3.1 Published 2019-08-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
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 ParseContentEncodingEntry of mkvparser.cc, there is a possible double free due to a missing reset of a freed pointer. This could lead to remote code execution with no additional execution privileges needed. User interaction is needed for exploitation. Product: Android. Versions: Android-7.0 Android-7.1.1 Android-7.1.2 Android-8.0 Android-8.1 Android-9. Android ID: A-127702368.

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

A double free vulnerability exists in the ParseContentEncodingEntry function of mkvparser.cc within Android's media framework. When a pointer is freed, it is not reset to NULL, allowing a subsequent free operation on the same pointer to cause memory corruption. This can be triggered by parsing a specially crafted MKV/Matroska video file, leading to remote code execution. User interaction is required (opening a malicious video file).

MitigationApply the vendor patch which resets freed pointers to NULL after deallocation in mkvparser.cc. Until the patch is available, exercise caution when opening MKV files from untrusted sources.

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
Ubuntu LinuxOperating system
Affected:= 16.04= 18.04= 19.04
AndroidOperating system
Affected:= 7.0= 7.1.1= 7.1.2= 8.0= 8.1= 9.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
High
Availability
High

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

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

  1. Check Android system version
    Run 'getprop ro.build.version.release' or check Settings > About Phone > Android version
    Affected if The version is 7.0, 7.1.1, 7.1.2, 8.0, 8.1, or 9.0
  2. Identify installed media framework libraries
    Search for libstagefright, libmkvparser, or similar media parsing libraries on the system (e.g., 'find /system/lib -name "*stagefright*"' or 'find /system/lib -name "*mkv*"')
    Affected if The mkvparser library exists on the device and is used by media playback components
  3. Check media library version
    Inspect the library binary version or check package version if available (e.g., 'dpkg -l | grep stagefright' on Ubuntu, 'rpm -qa | grep android' on Fedora)
    Affected if The library version matches the vulnerable Android versions (7.0-9.0 range) and has not been patched to reset freed pointers to NULL in ParseContentEncodingEntry
  4. Verify MKV playback capability
    Confirm the device can open and parse MKV/Matroska video files through the media framework
    Affected if MKV parsing is enabled and the vulnerable ParseContentEncodingEntry function in mkvparser.cc is called during file processing

The system is affected if it runs an unpatched Android 7.0-9.0 based OS or a Linux distribution with the vulnerable android-libstagefright library version corresponding to those Android releases, and the device has the capability to parse MKV video files.

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 patch which resets freed pointers to NULL after deallocation in mkvparser.cc. Until the patch is available, exercise caution when opening MKV files from untrusted sources.

Fix this in Fedora Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing16.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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