Menu

Star on GitHub · 3.2k

CVE-2007-4476

7.5 · HIGH

Buffer overflow in the safer_name_suffix function in GNU tar has unspecified attack vectors and impact, resulting in a "crashing stack."

Published Sep 5, 2007gnuCWE-119EPSS 14.90%

Overview

CVE-2007-4476 is a high-severity vulnerability affecting gnu tar. It was published on September 5, 2007 and has a CVSS 2.0 base score of 7.5 (HIGH).

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

Technical description

Buffer overflow in the safer_name_suffix function in GNU tar has unspecified attack vectors and impact, resulting in a "crashing stack."

Remediation

Check the references section for vendor advisories and patches from gnu. Update tar 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
gnutar>= 0, < 1.19Affected

Frequently asked questions

What is CVE-2007-4476?

CVE-2007-4476 is a high-severity vulnerability affecting gnu tar. It was published on September 5, 2007 and has a CVSS 2.0 base score of 7.5 (HIGH).

How severe is CVE-2007-4476?

This vulnerability has a CVSS 2.0 base score of 7.5, 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-2007-4476?

Check the references section for vendor advisories and patches from gnu. Update tar 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-2007-4476?

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

View all