Loading vulnerability…
CVE-2013-4694 encompasses stack-based buffer overflows in Winamp before version 5.64. A primary flaw occurs during skin-directory enumeration: Winamp insufficiently validates a skin-directory name, or the configured skin value, before copying it with lstrcpynW, allowing an oversized Unicode string to overflow a stack buffer. A separate condition occurs when an oversized value entered in the Library Search GUI field is passed to GetDlgItemTextW without adequate bounds validation. Both conditions can crash Winamp and may permit arbitrary code execution in the context of the user running the application.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 2 candidates as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Two stack-based buffer overflows in WinAmp 5.63 and potentially older releases. Bug #1 can enable code execution as the current user through a crafted skin package or winamp.ini; Bug #2 requires local access and an overlong WinAmp Library Search-field string. Failed exploitation can cause denial of service.
Multiple WinAmp buffer-overflow conditions, principally a remotely exploitable Unicode-based stack overflow in gen_jumpex.dll caused by an oversized skin directory name. Successful exploitation may permit code execution.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.