Skip to content
Fencer Vulns
medium 5.0

CVE-2005-0372 json

Directory traversal vulnerability in gftp before 2.0.18 for GTK+ allows remote malicious FTP servers to read arbitrary files via .. (dot do…

published 2005-02-17 21 y ago modified 2026-06-16 4 mo ago also EUVD-2005-0373

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

Summary

Directory traversal vulnerability in gftp before 2.0.18 for GTK+ allows remote malicious FTP servers to read arbitrary files via .. (dot dot) sequences in filenames returned from a LIST command.

Patch / fix

  • gnome gtk 2.0.18
  • gftp Debian 14, Debian 13, Debian 12 2.0.18-1

debian advisories DEBIAN-CVE-2005-0372

  • gftp RHEL 3 1:2.0.14-4
  • gftp RHEL 4 1:2.0.17-5

red hat advisories RHSA-2005:410

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-2005-0372 updated

security flaw

  • Red Hat Desktop version 3 gftp 2.0.14-4 Red Hat Enterprise Linux AS version 3 gftp 2.0.14-4 Red Hat Enterprise Linux AS version 4 gftp 2.0.17-5 Red Hat Enterprise Linux Desktop version 4 gftp 2.0.17-5 Red Hat Enterprise Linux ES version 3 gftp 2.0.14-4 Red Hat Enterprise Linux ES version 4 gftp 2.0.17-5
    +2 more products
    Red Hat Enterprise Linux WS version 3 gftp 2.0.14-4 Red Hat Enterprise Linux WS version 4 gftp 2.0.17-5
    fixed: vendor fix RHSA-2005:410

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.38% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

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

Classification

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

References

Sources

Fencer Vulns 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.