Menu

Star on GitHub · 3.2k

CVE-2010-4226

7.2 · HIGH

cpio, as used in build 2007.05.10, 2010.07.28, and possibly other versions, allows remote attackers to overwrite arbitrary files via a symlink within an RPM package archive.

Published Feb 6, 2014gnuCWE-59EPSS 2.93%

Overview

CVE-2010-4226 is a high-severity vulnerability affecting gnu cpio. It was published on February 6, 2014 and has a CVSS 3.1 base score of 7.2 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.2, rated HIGH. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

Technical description

cpio, as used in build 2007.05.10, 2010.07.28, and possibly other versions, allows remote attackers to overwrite arbitrary files via a symlink within an RPM package archive.

Remediation

Check the references section for vendor advisories and patches from gnu. Update cpio 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-2010-4226?

CVE-2010-4226 is a high-severity vulnerability affecting gnu cpio. It was published on February 6, 2014 and has a CVSS 3.1 base score of 7.2 (HIGH).

How severe is CVE-2010-4226?

This vulnerability has a CVSS 3.1 base score of 7.2, rated HIGH. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2010-4226?

Check the references section for vendor advisories and patches from gnu. Update cpio 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-2010-4226?

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

View all