SPlayer up to 3.7 Header buffer overflow

Summaryinfo

A vulnerability was found in SPlayer up to 3.7. It has been rated as critical. Impacted is an unknown function of the component Header Handler. The manipulation leads to buffer overflow. This vulnerability is documented as CVE-2011-10022. The attack can be initiated remotely. Additionally, an exploit exists.

Detailsinfo

A vulnerability was found in SPlayer up to 3.7. It has been rated as critical. This issue affects an unknown function of the component Header Handler. The manipulation with an unknown input leads to a buffer overflow vulnerability. Using CWE to declare the problem leads to 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, leading to a buffer overflow. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

SPlayer version 3.7 and earlier is vulnerable to a stack-based buffer overflow when processing HTTP responses containing an overly long Content-Type header. The vulnerability occurs due to improper bounds checking on the header value, allowing an attacker to overwrite the Structured Exception Handler (SEH) and execute arbitrary code. Exploitation requires the victim to open a media file that triggers an HTTP request to a malicious server, which responds with a crafted Content-Type header.

The weakness was released by xsploitedsec. It is possible to read the advisory at raw.githubusercontent.com. The identification of this vulnerability is CVE-2011-10022 since 08/18/2025. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details are unknown but a public exploit is available.

The exploit is available at exploit-db.com. It is declared as proof-of-concept.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at Exploit-DB (17243). Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Name

• SPlayer

Version

• 3.0
• 3.1
• 3.2
• 3.3
• 3.4
• 3.5
• 3.6
• 3.7

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion