Menu

Star on GitHub · 3.2k

CVE-2003-0613

4.6 · MEDIUM

Buffer overflow in zblast-svgalib of zblast 1.2.1 and earlier allows local users to execute arbitrary code via the high score file.

Published Aug 27, 2003zblastEPSS 0.46%

Overview

CVE-2003-0613 is a medium-severity vulnerability affecting zblast zblast. It was published on August 27, 2003 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 zblast-svgalib of zblast 1.2.1 and earlier allows local users to execute arbitrary code via the high score file.

Remediation

Check the references section for vendor advisories and patches from zblast. Update zblast 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
zblastzblast0Affected

Frequently asked questions

What is CVE-2003-0613?

CVE-2003-0613 is a medium-severity vulnerability affecting zblast zblast. It was published on August 27, 2003 and has a CVSS 2.0 base score of 4.6 (MEDIUM).

How severe is CVE-2003-0613?

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-2003-0613?

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

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

View all