CVE-2010-10017
BaseFortify
Publication date: 2025-08-30
Last updated on: 2025-09-02
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wm_downloader | wm_downloader | 3.1.2.2 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-120 | The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer. |
| CWE-134 | The product uses a function that accepts a format string as an argument, but the format string originates from an external source. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2010-10017 is a buffer overflow vulnerability in WM Downloader version 3.1.2.2 that occurs when the application processes a specially crafted .m3u playlist file. The application does not properly validate the input length, allowing an attacker to overwrite Structured Exception Handler (SEH) records. This enables the attacker to execute arbitrary code with the privileges of the current user when the malicious file is opened locally. [1, 2, 3, 4]
How can this vulnerability impact me? :
This vulnerability can allow a local attacker to execute arbitrary code on the affected system with the same privileges as the user running WM Downloader. This could lead to unauthorized actions such as running malicious programs, stealing data, or compromising system integrity and availability. [1, 2, 3, 4]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by identifying the presence of WM Downloader version 3.1.2.2 or earlier on the system and monitoring for the opening or import of specially crafted .m3u playlist files. Since the exploit involves a buffer overflow triggered by malformed M3U files, detection can include scanning for suspicious .m3u files with unusually large or malformed content. There are no specific commands provided in the resources, but you can check for the application version on Windows systems using commands like 'wmic product where "name like '%WM Downloader%'" get name, version' or by searching for .m3u files recently accessed or created. Additionally, monitoring for execution of unexpected processes or crashes related to WM Downloader when opening .m3u files may indicate exploitation attempts. [1, 2, 3, 4]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Avoid opening or importing .m3u playlist files from untrusted or unknown sources in WM Downloader version 3.1.2.2 or earlier. 2) If possible, uninstall WM Downloader or upgrade to a version that is not vulnerable (note that the product appears to be no longer supported). 3) Restrict user privileges to limit the impact of potential exploitation. 4) Use application whitelisting or endpoint protection to detect or block execution of malicious payloads. 5) Monitor and block suspicious .m3u files at the network or endpoint level. Since no official patch is available, these steps help reduce risk. [1]