CVE-2002-0178 json
uudecode, as available in the sharutils package before 4.2.1, does not check whether the filename of the uudecoded file is a pipe or symbol…
published 2002-05-29 24 y ago modified 2026-06-16 4 mo ago also EUVD-2002-0176
- cvss
- 7.2
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
uudecode, as available in the sharutils package before 4.2.1, does not check whether the filename of the uudecoded file is a pipe or symbolic link, which could allow attackers to overwrite files or execute commands.
Patch / fix
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-2002-0178 updated
security flaw
-
Red Hat Linux 6.2 Red Hat Linux 7.0 Red Hat Linux 7.1 Red Hat Linux 7.2fixed: vendor fix RHSA-2002:065
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
0.62% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
References
-
redhat.com
/support/errata/RHSA-2002-065.html
vendor-advisory, patch
-
linux-mandrake.com
/en/security/2002/MDKSA-2002-052.php
vendor-advisory
-
redhat.com
/support/errata/RHSA-2003-180.html
vendor-advisory
-
online.securityfocus.com
/advisories/4132
vendor-advisory
-
securityfocus.com
/bid/4742
vdb-entry
-
marc.info
/?l=bugtraq&m=103599320902432&w=2
mailing-list
-
kb.cert.org
/vuls/id/336083
third-party-advisory, us-government-resource
-
osvdb.org
/8274
vdb-entry
- aerasec.de /security/index.html?id=ae-200204-033&lang=en
-
iss.net
/security_center/static/9075.php
vdb-entry
Sources
- CVE List CVE-2002-0178
- NVD CVE-2002-0178
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.