CVE-2008-4610
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 · uneditedMPlayer allows remote attackers to cause a denial of service (application crash) via (1) a malformed AAC file, as demonstrated by lol-vlc.aac; or (2) a malformed Ogg Media (OGM) file, as demonstrated by lol-ffplay.ogm, different vectors than CVE-2007-6718.
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 confidenceMPlayer contains a denial of service vulnerability in its media file parsing logic. Specifically, processing a malformed AAC file (such as lol-vlc.aac) or a malformed OGM (Ogg Media) file (such as lol-ffplay.ogm) causes the application to crash. The vulnerability stems from insufficient validation or improper handling of malformed headers and data structures within these media container formats.
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<= 1.0_rc1= 0.90= 0.90_pre= 0.90_rc= 0.90_rc4= 0.91= 0.92= 0.92.1= 0.92_cvs= 1.0_pre1= 1.0_pre2= 1.0_pre3CVSS 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
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed MPlayer versionRun `mplayer -version` or check via package manager (e.g., `dpkg -l mplayer`, `rpm -q mplayer`)Affected if Version matches any of: <= 1.0_rc1, 0.90, 0.90_pre, 0.90_rc, 0.90_rc4, 0.91, 0.92, 0.92.1, 0.92_cvs, 1.0_pre1, 1.0_pre2, 1.0_pre3
-
Verify native AAC demuxer/decoder is in useMPlayer uses its native AAC decoder by default. Check configuration in ~/.mplayer/config or /etc/mplayer.conf for `ac` options. Default behavior parses AAC files using the native decoder.Affected if MPlayer is configured to use native AAC parsing (no alternative decoder specified) and opens a malformed AAC file
-
Verify OGM parsing is enabledMPlayer handles OGM files through its libavformat/ffmpeg integration or native demuxer. Default configuration enables OGM support.Affected if MPlayer default OGM demuxing is active and a malformed OGM file is opened
-
Confirm vulnerability trigger conditionThe crash occurs when MPlayer attempts to parse a malformed AAC file (e.g., lol-vlc.aac) or OGM file (e.g., lol-ffplay.ogm) using its native parsing path.Affected if A malformed AAC or OGM file is processed by an affected MPlayer version using its default demuxer/decoder configuration
You are affected if your MPlayer version matches the listed affected versions AND you open malformed AAC or OGM media files using MPlayer's default parsing configuration.
Generated from the published advisory. Verify against your own configuration.
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 dataUsers should avoid opening media files from untrusted sources. Administrators should update MPlayer to the latest version once a patch is available, as this vulnerability is fixed in later releases.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-4610 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2008-4610 in production — separate from our analysis above.
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.
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.
- 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