MplayerApplication

CVE-2006-1502

MEDIUM · 5.1 CVSS v2.0 Published 2006-03-30

Fix available

A fix is available. Upgrade to after 1.0_pre7try2 or later.

See remediation →

60/100

Remediation priority · Elevated

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Multiple integer overflows in MPlayer 1.0pre7try2 allow remote attackers to cause a denial of service and trigger heap-based buffer overflows via (1) a certain ASF file handled by asfheader.c that causes the asf_descrambling function to be passed a negative integer after the conversion from a char to an int or (2) an AVI file with a crafted wLongsPerEntry or nEntriesInUse value in the indx chunk, which is handled in aviheader.c.

Technical summary

dbcve analysis · high confidence

MPlayer 1.0pre7try2 contains multiple integer overflow vulnerabilities in its media file parsing code. The first flaw is in asfheader.c where conversion of a char to int in the asf_descrambling function can produce a negative integer, leading to heap-based buffer overflows when processing specially crafted ASF files. The second flaw exists in aviheader.c where malicious AVI files with crafted wLongsPerEntry or nEntriesInUse values in the indx chunk can trigger integer overflows and subsequent heap overflows.

MitigationUpgrade to a patched version of MPlayer that addresses these integer overflow vulnerabilities. If patching is not feasible, limit MPlayer's ability to process untrusted ASF/AVI media files from unknown or untrusted sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

MplayerApplication

Affected:<= 1.0_pre7try2

CVSS breakdown

From the vector

Attack vector: Network
Complexity: High
Authentication: None
Confidentiality: Partial
Integrity: Partial
Availability: Partial

AV:N/AC:H/Au:N/C:P/I:P/A:P

Am I affected?

dbcve checks

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

Verify MPlayer is installed

Run 'which mplayer' or 'mplayer -version' on the target system

Affected if MPlayer is not found on the system, the system is not affected by this vulnerability
Retrieve the installed MPlayer version

Execute 'mplayer -version' and note the version string in the output (typically shown in the first line)

Affected if The version cannot be determined or the command fails
Compare version to the affected range

Examine the version string obtained - look for versions 1.0_pre7try2 or earlier (note: version formats may appear as '1.0pre7try2' or similar)

Affected if The installed version is 1.0_pre7try2 or any earlier version (including 1.0pre7, 1.0pre6, etc.)
Determine exposure to malicious media files

Assess whether the MPlayer installation is used to process ASF or AVI files from untrusted or unknown sources

Affected if The system processes untrusted ASF or AVI media files using this vulnerable MPlayer version

The system is affected if MPlayer version 1.0_pre7try2 or earlier is installed AND it is used to process ASF or AVI files from untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Upgrade available Upgrade to a release after 1.0_pre7try2

Interim mitigation

Upgrade to a patched version of MPlayer that addresses these integer overflow vulnerabilities. If patching is not feasible, limit MPlayer's ability to process untrusted ASF/AVI media files from unknown or untrusted sources.

Fix this in Mplayer Scoped from the published advisory

Consultation3.0 h
Implementation6.0 h
Testing3.0 h
Review / QA2.0 h

14.0 hours of engineering $2,490

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2006-1502 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2006-1502?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to after 1.0_pre7try2 or later

Severity 5.1 Medium

Exploit likelihood EPSS, next 30 days 3.4%

Affects: Mplayer

Remediation

Need this fixed?

Fix this in Mplayer 14 hrs · Moderate

Typical engagement from $2,490

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2006-1502 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References