CVE-2017-10727
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 · uneditedWinamp 5.666 Build 3516(x86) might allow attackers to execute arbitrary code or cause a denial of service via a crafted .flv file, related to "Data from Faulting Address controls Branch Selection starting at in_mp3!DeleteAudioDecoder+0x000000000000762f."
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 confidenceMemory corruption vulnerability in Winamp 5.666 Build 3516's MP3 decoder plugin (in_mp3.dll) allows arbitrary code execution via crafted .flv files. The 'Data from Faulting Address controls Branch Selection' condition indicates attacker-controlled data corrupts memory and influences code execution flow, enabling arbitrary code execution or denial of service.
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= 5.666CVSS 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
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Verify Winamp is installedCheck for Winamp installation directory (commonly C:\Program Files\Winamp or C:\Program Files (x86)\Winamp) or search for winamp.exe on the systemAffected if Winamp executable is found on the system
-
Determine installed Winamp versionRight-click winamp.exe, select Properties, then go to the Details tab to view Product Version; alternatively, run winamp.exe and check Help > About WinampAffected if Version reported is 5.666 Build 3516 exactly
-
Confirm vulnerable MP3 decoder plugin existsLocate in_mp3.dll in the Winamp installation directory (typically in the plugins subfolder or root Winamp folder)Affected if in_mp3.dll exists and belongs to Winamp 5.666 Build 3516
-
Check if FLV file handling is activeInspect Winamp settings or file associations for .flv file type support; verify the MP3 decoder plugin is configured to handle media filesAffected if Winamp is configured to open or associate with .flv files using the in_mp3.dll plugin
User is affected if Winamp 5.666 Build 3516 is installed and the in_mp3.dll plugin is present and configured to handle .flv files.
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 dataAvoid opening untrusted .flv files in vulnerable Winamp versions. Consider migrating to actively maintained media players as Winamp is effectively abandonware with no official patch available.
- Consultation6.0 h
- Implementation30.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10727 — 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-2017-10727 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