Menu

Star on GitHub · 3.2k

CVE-1999-1553

10.0 · HIGH

Buffer overflow in XCmail 0.99.6 with autoquote enabled allows remote attackers to execute arbitrary commands via a long subject line.

Published May 1, 1999xcmailEPSS 5.98%

Overview

CVE-1999-1553 is a high-severity vulnerability affecting xcmail xcmail. It was published on May 1, 1999 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 XCmail 0.99.6 with autoquote enabled allows remote attackers to execute arbitrary commands via a long subject line.

Remediation

Check the references section for vendor advisories and patches from xcmail. Update xcmail 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-1999-1553?

CVE-1999-1553 is a high-severity vulnerability affecting xcmail xcmail. It was published on May 1, 1999 and has a CVSS 2.0 base score of 10.0 (HIGH).

How severe is CVE-1999-1553?

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-1999-1553?

Check the references section for vendor advisories and patches from xcmail. Update xcmail 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-1999-1553?

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