How severe is CVE-2003-1140?

CVE-2003-1140 has a CVSS 2.0 base score of 10.0, rated critical severity.

Is CVE-2003-1140 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 6% (93rd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2003-1140?

CVE-2003-1140 primarily affects Musicqueue. In total, 6 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2003-1140?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2003-1140 published?

CVE-2003-1140 was published on 2003-10-27 and last updated on 2026-06-16.

CVE-2003-1140

CVE-2003-1140 is a critical-severity vulnerability in Musicqueue with a CVSS 2.0 base score of 10.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Critical (CVSS 2.0 base score 10.0)
EPSS exploit prediction: 6% (93rd percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Musicqueue
Published: 2003-10-27
Last modified: 2026-06-16

Description

Buffer overflow in Musicqueue 1.2.0 allows local users to execute arbitrary code via a long language variable in the configuration file.

Frequently asked questions

What is CVE-2003-1140?: Buffer overflow in Musicqueue 1.2.0 allows local users to execute arbitrary code via a long language variable in the configuration file.
How severe is CVE-2003-1140?: CVE-2003-1140 has a CVSS 2.0 base score of 10.0, rated critical severity.
Is CVE-2003-1140 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 6% (93rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2003-1140?: CVE-2003-1140 primarily affects Musicqueue. In total, 6 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2003-1140?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2003-1140 published?: CVE-2003-1140 was published on 2003-10-27 and last updated on 2026-06-16.

References

Affected products (6)

cpe:2.3:a:musicqueue:musicqueue:0.9:*:*:*:*:*:*:*
cpe:2.3:a:musicqueue:musicqueue:0.9.1:*:*:*:*:*:*:*
cpe:2.3:a:musicqueue:musicqueue:0.9.2:*:*:*:*:*:*:*
cpe:2.3:a:musicqueue:musicqueue:1.0:*:*:*:*:*:*:*
cpe:2.3:a:musicqueue:musicqueue:1.1:*:*:*:*:*:*:*
cpe:2.3:a:musicqueue:musicqueue:1.1.1:*:*:*:*:*:*:*

More vulnerabilities in Musicqueue

CVE-2003-1139 — Medium (CVSS 5.0): Musicqueue 1.2.0 allows local users to overwrite arbitrary files by triggering a segmentation fault and using a symlink…

All CVEs affecting Musicqueue →