Mplayer vulnerabilitiesRanked by how likely they are to be used.

Product22 versions
The short answer

Mplayer is made by Mplayerhq. We track 19 published vulnerabilities in it, across 22 versions. None of them is on the list of flaws known to be exploited today. If you run Mplayer, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Mplayer vulnerabilities are being exploited?

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

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

Exploit likelihood

Which Mplayer 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. 4.2%

    FFmpeg before 0.5.4, as used in MPlayer and other products, allows remote attackers to cause a denial of service (heap memory corruption and application crash) or possibly execute arbitrary code via a malformed...

    CVSS6.8Published20 May 2011
  2. 4.2%

    flicvideo.c in libavcodec 0.6 and earlier in FFmpeg, as used in MPlayer and other products, allows remote attackers to execute arbitrary code via a crafted flic file, related to an "arbitrary offset dereference...

    CVSS6.8Published30 Sep 2010
  3. 3.0%

    FFmpeg before 0.5.4, as used in MPlayer and other products, allows remote attackers to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via a malformed WMV file.

    CVSS6.8Published20 May 2011
  4. 1.7%

    The VC-1 decoding functionality in FFmpeg before 0.5.4, as used in MPlayer and other products, does not properly restrict read operations, which allows remote attackers to have an unspecified impact via a crafted...

    CVSS9.3Published20 May 2011
  5. 0.9%

    The MPlayer Project v1.5 was discovered to contain a heap use-after-free resulting in a double free in the preinit function at libvo/vo_v4l2.c.

    CVSS5.5Published14 Jul 2022
  6. 0.4%

    Mplayer SVN-r38374-13.0.1 is vulnerable to Memory Leak via vf.c and vf_vo.c.

    CVSS5.5Published15 Sep 2022
  7. 0.4%

    Certain The MPlayer Project products are vulnerable to Buffer Overflow via function gen_sh_video () of mplayer/libmpdemux/demux_mov.c.

    CVSS5.5Published15 Sep 2022
  8. 0.4%

    Certain The MPlayer Project products are vulnerable to Buffer Overflow via function mov_build_index() of libmpdemux/demux_mov.c.

    CVSS5.5Published15 Sep 2022
  9. 0.4%

    Certain The MPlayer Project products are vulnerable to Buffer Overflow via function mp_getbits() of libmpdemux/mpeg_hdr.c which affects mencoder and mplayer.

    CVSS5.5Published15 Sep 2022
Precursor Intelligence

Running Mplayer? 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 19 published vulnerabilities listed under the name Mplayer, across 22 versions.

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

Create a Precursor Intelligence account and track Mplayer. 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.