CVE-2000-0049
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 · uneditedBuffer overflow in Winamp client allows remote attackers to execute commands via a long entry in a .pls file.
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 confidenceBuffer overflow vulnerability in Winamp media player allows remote attackers to execute arbitrary commands by crafting a malicious .pls playlist file with overly long entries. When the victim opens the crafted .pls file, the buffer overflow occurs, potentially giving the attacker code execution with the same privileges as the Winamp user.
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= 2.0= 2.10CVSS 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
- Local
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/Au:N/C:C/I:C/A:C
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.
-
Check if Winamp is installedLook for winamp.exe on the system - common locations include C:\Program Files\Winamp\ and C:\Program Files (x86)\Winamp\. Use File Explorer or a command like 'dir /s /b C:\winamp.exe' to search drives.Affected if Winamp executable is found on the system
-
Identify the installed Winamp versionRight-click on winamp.exe, select Properties, and check the Version tab. Alternatively, run winamp.exe and look at the title bar or About section.Affected if Version shows 2.0 or 2.10 exactly
-
Confirm the exact version numberCross-reference the version with the file properties details - look for Product Version or File Version fields.Affected if The version is listed as 2.0 or 2.10 (not a later version)
-
Check if .pls files are associated with WinampLook for .pls file associations - right-click any .pls file, select Properties, then 'Opens with'. Or check in Windows Settings > Apps > Default Apps > Choose default apps by file type.Affected if Winamp is set as the default handler for .pls playlist files
A user is affected if Winamp versions 2.0 or 2.10 is installed and configured to open .pls playlist files, allowing the buffer overflow to trigger when a malicious .pls file is opened.
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 dataReplace Winamp with a currently-maintained media player, and avoid opening playlist files from untrusted sources. Since Winamp is discontinued with no security updates available, migration to an alternative player is the only viable remediation.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0049 — 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-2000-0049 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