Menu

Star on GitHub · 3.2k

CVE-2004-0402

4.6 · MEDIUM

Buffer overflow in xpcd-svga in xpcd before 2.08, and possibly other versions, may allow local users to execute arbitrary code.

Published Jul 7, 2004xpcdEPSS 0.48%

Overview

CVE-2004-0402 is a medium-severity vulnerability affecting xpcd xpcd. It was published on July 7, 2004 and has a CVSS 2.0 base score of 4.6 (MEDIUM).

This vulnerability has a CVSS 2.0 base score of 4.6, rated MEDIUM. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical description

Buffer overflow in xpcd-svga in xpcd before 2.08, and possibly other versions, may allow local users to execute arbitrary code.

Remediation

Check the references section for vendor advisories and patches from xpcd. Update xpcd 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-2004-0402?

CVE-2004-0402 is a medium-severity vulnerability affecting xpcd xpcd. It was published on July 7, 2004 and has a CVSS 2.0 base score of 4.6 (MEDIUM).

How severe is CVE-2004-0402?

This vulnerability has a CVSS 2.0 base score of 4.6, rated MEDIUM. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2004-0402?

Check the references section for vendor advisories and patches from xpcd. Update xpcd 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-2004-0402?

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

View all