CVE-2017-10726
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 may be used as a return value starting at f263!GetWinamp5SystemComponent+0x0000000000001951."
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 confidenceBuffer overflow vulnerability in Winamp 5.666 Build 3516 when parsing malformed .flv files. The vulnerability occurs in the GetWinamp5SystemComponent function at a specific offset, allowing attackers to overwrite return addresses on the stack and achieve arbitrary code execution or cause a 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 installationCheck for the presence of Winamp executable (winamp.exe) in typical installation directories such as C:\Program Files\Winamp\ or C:\Program Files (x86)\Winamp\, or search the system using 'where winamp.exe' commandAffected if Winamp is found installed on the system
-
Confirm installed versionRight-click winamp.exe, select Properties, then view the Details tab to check the File Version. Alternatively, run 'winamp.exe /?' or check Help > About Winamp within the applicationAffected if The version is exactly 5.666 Build 3516
-
Check FLV playback capabilityAttempt to open any .flv file in Winamp, or check File Types in Winamp preferences under Options > Preferences > File Types to confirm FLV association is enabledAffected if FLV file type support is enabled and Winamp can load .flv files
-
Inspect for suspicious FLV filesSearch user directories (Downloads, Desktop, Documents) for recently modified .flv files from untrusted or unknown sources, or check Winamp recent playlist history for recently played .flv filesAffected if Malformed or untrusted .flv files exist on the system that have been opened with Winamp
-
Check for crash logs or异常Review Windows Event Viewer Application logs for winamp.exe crash events, or check for .mdmp crash dump files in the Winamp installation folderAffected if Recent Winamp crashes related to FLV file processing are recorded
A user is affected if Winamp version 5.666 Build 3516 is installed and FLV file playback is enabled, with any risk of exposure to malformed .flv files from untrusted sources.
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 dataSince Winamp development has effectively ceased, there is no vendor patch available. Organizations should implement endpoint detection rules to block or warn on suspicious .flv file execution, educate users about risks of opening media files from untrusted sources, and consider deploying alternative media players with active security support.
- 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-2017-10726 — 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-10726 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