Skip to content
Fencer Intel
medium 5.8

CVE-2010-4651 json

Directory traversal vulnerability in util.c in GNU patch 2.6.1 and earlier allows user-assisted remote attackers to create or overwrite arb…

published 15y ago modified 4mo ago also EUVD-2010-4616

cvss
5.8
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
4.9%
EPSS 4.9% chance of exploitation in 30 days, percentile 92%
public exploits
0
none known

Summary

Directory traversal vulnerability in util.c in GNU patch 2.6.1 and earlier allows user-assisted remote attackers to create or overwrite arbitrary files via a filename that is specified with a .. (dot dot) or full pathname, a related issue to CVE-2010-1679.

Patch / fix

  • patch SLES for SAP 11 SP4, SLES 11 SP4, SLES 11 SP3-TERADATA +2 more 2.5.9-252.22.7.1

suse advisories SUSE-SU-2018:1162-1

  • patch openSUSE Tumbleweed 2.7.5-1.112

opensuse advisories openSUSE-SU-2024:10379-1

Is CVE-2010-4651 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2010-4651 updated cvss 2.1

patch: directory traversal flaw allows for arbitrary file creation

  • Red Hat Enterprise Linux 4 patch Red Hat Enterprise Linux 5 patch Red Hat Enterprise Linux 6 patch
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

4.87% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 5.8 AV:N/AC:M/Au:N/C:N/I:P/A:P

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.