dbcve.org
Streaming MediaApplication · Live555

CVE-2019-7732

HIGH · 7.5 CVSS v3.0 Published 2019-02-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
In Live555 0.95, a setup packet can cause a memory leak leading to DoS because, when there are multiple instances of a single field (username, realm, nonce, uri, or response), only the last instance can ever be freed.

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 Live555 0.95, RTSP setup packet parsing contains a memory leak when handling duplicate header fields (username, realm, nonce, uri, or response). The parser allocates memory for each field instance but only frees the last occurrence, causing progressive memory exhaustion with repeated malformed requests and leading to denial of service.

MitigationApply vendor patch for CVE-2019-7732 to fix the memory management in RTSP header field parsing, or upgrade to a patched version of Live555. Implement request rate limiting as a temporary defense to mitigate exploitation.

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:= 0.95

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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. Identify Live555 installation and version
    Locate the Live555 library files (libliveMedia.so, libBasicUsageEnvironment.so, libGroupsock.so, libUsageEnvironment.so) or the live555 MediaServer binary. Run 'live555MediaServer -v' or check the binary/library version using 'file' and review any version strings with 'strings' or 'grep -r "0.95"' in the Live555 installation directory.
    Affected if The installed version is exactly 0.95 of Live555 Streaming Media.
  2. Confirm RTSP server is enabled
    Check if the Live555 RTSP server process (live555MediaServer or similar) is running. Use 'ps aux | grep live555' or review systemd service status if deployed as a service. Verify the server configuration file (often 'live555.conf' or embedded in the application) permits RTSP connections.
    Affected if An RTSP server component built on Live555 0.95 is actively running and accepting connections.
  3. Check for memory exhaustion patterns
    Monitor memory usage of the live555 MediaServer process over time using 'ps -o pid,vsz,rss,comm -p <pid>' or 'top -p <pid>'. Look for progressive RSS (Resident Set Size) growth that does not stabilize, especially under repeated RTSP client connection attempts.
    Affected if The Live555 RTSP server process exhibits continuous memory growth without stabilization during normal or repeated RTSP request handling.
  4. Inspect RTSP request handling logs
    Review Live555 server logs for repeated malformed RTSP requests or evidence of duplicate header field parsing. Check if the server logs show 'RTSP' protocol messages, particularly surrounding authentication header processing (username, realm, nonce, uri, response fields).
    Affected if The server processes RTSP requests containing duplicate authentication header fields and shows abnormal behavior or memory growth.

A user is affected if they are running Live555 Streaming Media version 0.95 with an active RTSP server that handles client connections, as the memory leak only manifests during RTSP header field parsing of malformed requests.

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 vendor patch for CVE-2019-7732 to fix the memory management in RTSP header field parsing, or upgrade to a patched version of Live555. Implement request rate limiting as a temporary defense to mitigate exploitation.

Fix this in Streaming Media Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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