Streaming Media vulnerabilitiesRanked by how likely they are to be used.

Product559 versions
The short answer

Streaming Media is made by Live555. We track 8 published vulnerabilities in it, across 559 versions. None of them is on the list of flaws known to be exploited today. If you run Streaming Media, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Streaming Media vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Streaming Media's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Streaming Media flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 28%

    The parseRTSPRequestString function in Live Networks Live555 Streaming Media 2013.11.26, as used in VideoLAN VLC Media Player, allows remote attackers to cause a denial of service (crash) and possibly execute...

    CVSS7.5Published23 Jan 2014
  2. 17%

    The parseRTSPRequestString function in Live Networks Live555 Streaming Media 2011.08.13 through 2013.11.25, as used in VideoLAN VLC Media Player, allows remote attackers to cause a denial of service (crash) and...

    CVSS7.5Published23 Jan 2014
  3. 3.2%

    liblivemedia in Live555 before 2019.02.03 mishandles the termination of an RTSP stream after RTP/RTCP-over-RTSP has been set up, which could lead to a Use-After-Free error that causes the RTSP server to crash...

    CVSS9.8Published4 Feb 2019
  4. 2.2%

    In Live555 before 2019.02.27, malformed headers lead to invalid memory access in the parseAuthorizationHeader function.

    CVSS9.8Published28 Feb 2019
  5. 1.7%

    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...

    CVSS9.8Published20 Aug 2019
  6. 1.6%

    In Live555 0.95, there is a buffer overflow via a large integer in a Content-Length HTTP header because handleRequestBytes has an unrestricted memmove.

    CVSS7.5Published11 Feb 2019
  7. 1.4%

    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.

    CVSS7.5Published11 Feb 2019
  8. 1.1%

    Vulnerability in the AC3AudioFileServerMediaSubsession, ADTSAudioFileServerMediaSubsession, and AMRAudioFileServerMediaSubsessionLive OnDemandServerMediaSubsession subclasses in Networks LIVE555 Streaming Media...

    CVSS7.5Published29 Apr 2021
Precursor Intelligence

Running Streaming Media? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 8 published vulnerabilities listed under the name Streaming Media, across 559 versions.

None of Streaming Media's vulnerabilities is on the list of flaws known to be exploited today.

Create a Precursor Intelligence account and track Streaming Media. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.