CVE-2017-10728
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 "Error Code (0xe06d7363) starting at wow64!Wow64NotifyDebugger+0x000000000000001d."
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 · moderate confidenceWinamp 5.666 Build 3516 contains a memory corruption vulnerability when parsing specially crafted FLV files. The flaw triggers during FLV processing and can lead to arbitrary code execution or denial of service, as indicated by the Windows exception at wow64!Wow64NotifyDebugger.
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 installationCheck for winamp.exe in typical installation directories (C:\Program Files\Winamp\winamp.exe or C:\Program Files (x86)\Winamp\winamp.exe), or search for the executable using Windows Search or Get-ChildItem -Recurse for winamp.exeAffected if Winamp is not found on the system, the user is not affected
-
Determine installed Winamp versionRight-click winamp.exe, select Properties, then Details tab to view File Version; alternatively run "winamp.exe /?'" or check the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Winamp or HKEY_CURRENT_USER\SOFTWARE\Winamp for the version keyAffected if Installed version is not 5.666 exactly, the user is not affected (only 5.666 is vulnerable)
-
Check if FLV file association existsOpen Default Programs or File Type settings in Windows, search for .flv extension, and verify if Winamp is listed as the handler; alternatively check registry under HKEY_CLASSES_ROOT\.flv for the ProgIDAffected if Winamp is not associated with .flv files, the exploit surface is not present even on version 5.666
User is affected only if Winamp version 5.666 is installed AND Winamp is configured to open or handle .flv files, as the vulnerability is triggered specifically during FLV parsing.
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 dataDo not open untrusted or unknown .flv files in Winamp. Consider migrating to actively maintained media players, as Winamp is no longer actively developed.
- Consultation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10728 — 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-10728 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