Menu

Star on GitHub · 3.2k

CVE-2003-1135

2.6 · LOW

Buffer overflow in Yahoo!

Published Dec 31, 2003yahooEPSS 4.52%

Overview

CVE-2003-1135 is a low-severity vulnerability affecting yahoo messenger. It was published on December 31, 2003 and has a CVSS 2.0 base score of 2.6 (LOW).

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

Technical description

Buffer overflow in Yahoo! Messenger 5.6 allows remote attackers to cause a denial of service (crash) via a file send request (sendfile) with a large number of "%" (percent) characters after the Yahoo ID.

Remediation

Check the references section for vendor advisories and patches from yahoo. Update messenger 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-1135?

CVE-2003-1135 is a low-severity vulnerability affecting yahoo messenger. It was published on December 31, 2003 and has a CVSS 2.0 base score of 2.6 (LOW).

How severe is CVE-2003-1135?

This vulnerability has a CVSS 2.0 base score of 2.6, rated LOW. 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-1135?

Check the references section for vendor advisories and patches from yahoo. Update messenger 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-1135?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2003-1135 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 LOW CVEs from 2003

View all