dbcve.org
WinampApplication

CVE-2017-10725

HIGH · 7.3 CVSS v3.0 Published 2017-07-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated

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 · unedited
Winamp 5.666 Build 3516(x86) allows attackers to execute arbitrary code or cause a denial of service via a crafted .flv file, related to "Data from Faulting Address controls Code Flow starting at in_flv!winampGetInModule2+0x00000000000009a8."

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 confidence

Winamp 5.666's FLV input plugin (in_flv.dll) contains a memory corruption vulnerability where crafted data in a malicious .flv file controls code flow (arbitrary write primitive), enabling remote code execution or denial of service.

MitigationAvoid opening untrusted or unverified .flv files in Winamp until a vendor patch is available; consider endpoint detection/response tools to block suspicious file types.

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
WinampApplication
Affected:= 5.666

CVSS 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
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Winamp installation
    Check for Winamp installation directory (typically C:\Program Files\Winamp or C:\Program Files (x86)\Winamp)
    Affected if Winamp is installed on the system
  2. Identify installed Winamp version
    Right-click winamp.exe, select Properties, then Details to view the File Version; or run 'winamp.exe /?' or check Help > About Winamp
    Affected if Version displayed is exactly 5.666
  3. Locate the FLV input plugin
    Search for in_flv.dll within the Winamp installation directory and any plugins subfolders
    Affected if in_flv.dll exists in the Winamp installation folder
  4. Verify FLV file association or plugin is active
    Check Winamp preferences > Plugins > Input or verify .flv file type association in Windows (right-click any .flv file > Open with > Choose default app)
    Affected if FLV files are associated with Winamp or the in_flv.dll plugin is listed as enabled in Winamp's plugin configuration

If Winamp version 5.666 is installed with the in_flv.dll plugin present and FLV file support enabled, the environment is affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Avoid opening untrusted or unverified .flv files in Winamp until a vendor patch is available; consider endpoint detection/response tools to block suspicious file types.

Fix this in Winamp Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-10725 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-10725 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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