dbcve.org
Streaming MediaApplication · Live555

CVE-2019-15232

CRITICAL · 9.8 CVSS v3.1 Published 2019-08-20
Fix available
A fix is available. Upgrade to 2019-08-16 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Live555 before 2019.08.16 has a Use-After-Free because GenericMediaServer::createNewClientSessionWithId can generate the same client session ID in succession, which is mishandled by the MPEG1or2 and Matroska file demultiplexors.

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

Live555 streaming media library before 2019.08.16 contains a Use-After-Free vulnerability where GenericMediaServer::createNewClientSessionId can generate duplicate session IDs in succession. The MPEG1or2 and Matroska file demultiplexors fail to properly handle this session ID collision, leading to a Use-After-Free condition that can be exploited for remote code execution.

MitigationUpgrade Live555 to version 2019.08.16 or later, which contains the fix for proper session ID collision handling in the affected demultiplexors.

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
Streaming MediaApplication
Affected:< 2019-08-16

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Locate Live555 library files
    Search for liblivemedia or live555 shared libraries on the system using commands like 'find / -name "*live*" -o -name "*livemedia*"' or check common library directories (/usr/lib, /usr/local/lib, etc.)
    Affected if Live555 library files are not found on the system (not vulnerable, not installed)
  2. Identify the installed Live555 version
    Check the library file's version metadata using 'ls -la' for modification dates, or run 'strings' on the library to search for version strings like '2019.08.16' or check the binary/demuxer component version if accessible via '--version' or similar
    Affected if The version cannot be determined or is earlier than the 2019.08.16 release date
  3. Verify the library version against the affected range
    Compare the identified version to the known vulnerable range: any version released before 2019.08.16. If version information is unavailable, examine the library file's last modification date
    Affected if The installed version is dated or released before August 16, 2019, or the version string is less than 2019.08.16
  4. Check for MPEG1or2 or Matroska demultiplexor usage
    Identify if the Live555 deployment processes MPEG1, MPEG2, or Matroska (.mkv) media files by reviewing application logs, configuration files, or network traffic metadata that reveals the media container type being streamed
    Affected if MPEG1or2 or Matroska file demultiplexors are actively being used to stream media content

A user is affected if Live555 library version is identified as older than 2019.08.16 AND the system is actively demultiplexing MPEG1or2 or Matroska media streams.

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.

dbcve · scoped
Upgrade available Upgrade to 2019-08-16 or later
Fixed in 2019-08-16
Interim mitigation

Upgrade Live555 to version 2019.08.16 or later, which contains the fix for proper session ID collision handling in the affected demultiplexors.

Recommended fix High confidence

Live555 Streaming Media version 2019.08.16 or later

  1. 1. Identify the Live555 library or package currently in use in your project or system
  2. 2. Check the current version of Live555 (typically found in source code, build files, or package manager)
  3. 3. Obtain the fixed version (2019.08.16 or later) from the official Live555 source (www.live555.com)
  4. 4. Replace the existing Live555 library files with the updated version
  5. 5. Rebuild and recompile any applications that link against the Live555 library
  6. 6. Test the media streaming functionality to ensure the fix works and no regressions were introduced

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Streaming Media Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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