Skip to content
Fencer Vulns
low 2.1

CVE-2005-0990 json

unshar (unshar.c) in sharutils 4.2.1 allows local users to overwrite arbitrary files via a symlink attack on the unsh.X temporary file.

published 2005-04-06 21 y ago modified 2026-06-16 4 mo ago also EUVD-2005-0991

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

Summary

unshar (unshar.c) in sharutils 4.2.1 allows local users to overwrite arbitrary files via a symlink attack on the unsh.X temporary file.

Patch / fix

  • sharutils Debian 14, Debian 13, Debian 12 1:4.2.1-13

debian advisories DEBIAN-CVE-2005-0990

  • sharutils RHEL 3 4.2.1-16.2
  • sharutils RHEL 4 4.2.1-22.2

red hat advisories RHSA-2005:377

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-0990 updated

security flaw

  • Red Hat Desktop version 3 sharutils 4.2.1-16.2 Red Hat Enterprise Linux AS version 3 sharutils 4.2.1-16.2 Red Hat Enterprise Linux AS version 4 sharutils 4.2.1-22.2 Red Hat Enterprise Linux Desktop version 4 sharutils 4.2.1-22.2 Red Hat Enterprise Linux ES version 3 sharutils 4.2.1-16.2 Red Hat Enterprise Linux ES version 4 sharutils 4.2.1-22.2
    +2 more products
    Red Hat Enterprise Linux WS version 3 sharutils 4.2.1-16.2 Red Hat Enterprise Linux WS version 4 sharutils 4.2.1-22.2
    fixed: vendor fix RHSA-2005:377

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

CVSS scores

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

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.