Skip to content
Fencer Vulns
high 7.2

CVE-2000-1134 json

Multiple shell programs on various Unix systems, including (1) tcsh, (2) csh, (3) sh, and (4) bash, follow symlinks when processing << redi…

published 2000-12-19 25 y ago modified 2026-06-16 4 mo ago also EUVD-2000-1119

cvss
7.2
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.4%
EPSS 1.4% chance of exploitation in 30 days, percentile 72%
public exploits
2
Exploit-DB

Summary

Multiple shell programs on various Unix systems, including (1) tcsh, (2) csh, (3) sh, and (4) bash, follow symlinks when processing << redirects (aka here-documents or in-here documents), which allows local users to overwrite files of other users via a symlink attack.

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-2000-1134 updated

security flaw

  • Red Hat Linux 5.2 Red Hat Linux 6.0 Red Hat Linux 6.1 Red Hat Linux 6.2 Red Hat Linux 7.0 Red Hat Linux 7.0j
    fixed: vendor fix RHSA-2000:121

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

Timeline

  1. First public exploit (EDB-20436)
  2. Published

Exploit prediction

1.42% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • EDB-20436 Apple Mac OSX 10 / HP-UX 9/10/11 / Mandriva 6/7 / RedHat 5/6 / SCO 5 / IRIX 6 - Shell Redirection Race Condition local, 2000-01-02
  • EDB-217 UUCP - File Creation/Overwriting Symlinks local, 2000-12-04
  • securityfocus.com http://www.securityfocus.com/bid/2006 referenced PoC, tagged "exploit" by a source, unverified

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

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.