CVE-2011-10023

CVE-2011-10023 is a high-severity vulnerability with a CVSS 4.0 base score of 8.4. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-121.

Key facts

Description

MJM QuickPlayer (also known as MJM Player) version 2010 contains a stack-based buffer overflow vulnerability triggered by opening a malicious .s3m music file. The flaw occurs due to improper bounds checking in the file parser, allowing an attacker to overwrite memory and execute arbitrary code. Exploitation is achieved via a crafted payload that bypasses DEP and ASLR protections using ROP techniques, and requires user interaction to open the file.

Frequently asked questions

What is CVE-2011-10023?
MJM QuickPlayer (also known as MJM Player) version 2010 contains a stack-based buffer overflow vulnerability triggered by opening a malicious .s3m music file. The flaw occurs due to improper bounds checking in the file parser, allowing an attacker to overwrite memory and execute arbitrary code. Exploitation is achieved via a crafted payload that bypasses DEP and ASLR protections using ROP techniques, and requires user interaction to open the file.
How severe is CVE-2011-10023?
CVE-2011-10023 has a CVSS 4.0 base score of 8.4, rated high severity.
Is CVE-2011-10023 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (24th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2011-10023?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2011-10023 have an EU (EUVD) identifier?
Yes. CVE-2011-10023 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2011-5254.
When was CVE-2011-10023 published?
CVE-2011-10023 was published on 2025-08-20 and last updated on 2026-06-16.

References

Other CWE-121 (Stack-based Buffer Overflow) vulnerabilities

Browse all CWE-121 (Stack-based Buffer Overflow) vulnerabilities →