Menu

Star on GitHub · 3.2k

CVE-2005-1679

5.1 · MEDIUM

Stack-based buffer overflow in the error directive in picasm 1.12b and earlier allows attackers to execute arbitrary code via a long error message.

Published May 20, 2005timo_rossiEPSS 7.41%

Overview

CVE-2005-1679 is a medium-severity vulnerability affecting timo_rossi picasm. It was published on May 20, 2005 and has a CVSS 2.0 base score of 5.1 (MEDIUM).

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

Technical description

Stack-based buffer overflow in the error directive in picasm 1.12b and earlier allows attackers to execute arbitrary code via a long error message.

Remediation

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

Frequently asked questions

What is CVE-2005-1679?

CVE-2005-1679 is a medium-severity vulnerability affecting timo_rossi picasm. It was published on May 20, 2005 and has a CVSS 2.0 base score of 5.1 (MEDIUM).

How severe is CVE-2005-1679?

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

How do I fix or remediate CVE-2005-1679?

Check the references section for vendor advisories and patches from timo_rossi. Update picasm 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-2005-1679?

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

View all