Menu

Star on GitHub · 3.2k

CVE-2003-1140

10.0 · HIGH

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

Published Oct 27, 2003musicqueueEPSS 6.24%

Overview

CVE-2003-1140 is a high-severity vulnerability affecting musicqueue musicqueue. It was published on October 27, 2003 and has a CVSS 2.0 base score of 10.0 (HIGH).

This vulnerability has a CVSS 2.0 base score of 10.0, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

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

Remediation

Check the references section for vendor advisories and patches from musicqueue. Update musicqueue to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-2003-1140?

CVE-2003-1140 is a high-severity vulnerability affecting musicqueue musicqueue. It was published on October 27, 2003 and has a CVSS 2.0 base score of 10.0 (HIGH).

How severe is CVE-2003-1140?

This vulnerability has a CVSS 2.0 base score of 10.0, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2003-1140?

Check the references section for vendor advisories and patches from musicqueue. Update musicqueue to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2003-1140?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2003-1140 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2003

View all