CVE-2005-1751 json
Race condition in shtool 2.0.1 and earlier allows local users to create or modify arbitrary files via a symlink attack on the .shtool.$$ te…
published 2005-05-25 21 y ago modified 2026-06-16 4 mo ago also EUVD-2005-1753
- cvss
- 3.7
- 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 33%
- public exploits
- 0
- none known
Summary
Race condition in shtool 2.0.1 and earlier allows local users to create or modify arbitrary files via a symlink attack on the .shtool.$$ temporary file, a different vulnerability than CVE-2005-1759.
Patch / fix
- shtool Debian 14, Debian 13, Debian 12 2.0.1-2
- mysql-ocaml Debian 14, Debian 13, Debian 12 1.0.3-6
debian advisories DEBIAN-CVE-2005-1751
- php RHEL 3 4.3.2-24.ent
- php RHEL 4 4.3.9-3.7
- php-gd RHEL 4 4.3.9-3.7
- php-imap RHEL 3 4.3.2-24.ent
- php-imap RHEL 4 4.3.9-3.7
- php-ldap RHEL 3 4.3.2-24.ent
- php-ldap RHEL 4 4.3.9-3.7
- php-odbc RHEL 3 4.3.2-24.ent
red hat advisories RHSA-2005:564
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-1751 updated
shtool: insecure temporary file creation
-
Red Hat Desktop version 3 php 4.3.2-24.ent, php-imap 4.3.2-24.ent, php-ldap 4.3.2-24.ent, php-odbc 4.3.2-24.ent, php-mysql 4.3.2-24.ent, php-pgsql 4.3.2-24.ent Red Hat Enterprise Linux AS version 3 php 4.3.2-24.ent, php-imap 4.3.2-24.ent, php-ldap 4.3.2-24.ent, php-odbc 4.3.2-24.ent, php-mysql 4.3.2-24.ent, php-pgsql 4.3.2-24.ent Red Hat Enterprise Linux AS version 4 php 4.3.9-3.7, php-gd 4.3.9-3.7, php-imap 4.3.9-3.7, php-ldap 4.3.9-3.7, php-odbc 4.3.9-3.7, php-pear 4.3.9-3.7, +7 more Red Hat Enterprise Linux Desktop version 4 php 4.3.9-3.7, php-gd 4.3.9-3.7, php-imap 4.3.9-3.7, php-ldap 4.3.9-3.7, php-odbc 4.3.9-3.7, php-pear 4.3.9-3.7, +7 more Red Hat Enterprise Linux ES version 3 php 4.3.2-24.ent, php-imap 4.3.2-24.ent, php-ldap 4.3.2-24.ent, php-odbc 4.3.2-24.ent, php-mysql 4.3.2-24.ent, php-pgsql 4.3.2-24.ent Red Hat Enterprise Linux ES version 4 php 4.3.9-3.7, php-gd 4.3.9-3.7, php-imap 4.3.9-3.7, php-ldap 4.3.9-3.7, php-odbc 4.3.9-3.7, php-pear 4.3.9-3.7, +7 morefixed: vendor fix RHSA-2005:564
+2 more productsfewer
Red Hat Enterprise Linux WS version 3 php 4.3.2-24.ent, php-imap 4.3.2-24.ent, php-ldap 4.3.2-24.ent, php-odbc 4.3.2-24.ent, php-mysql 4.3.2-24.ent, php-pgsql 4.3.2-24.ent Red Hat Enterprise Linux WS version 4 php 4.3.9-3.7, php-gd 4.3.9-3.7, php-imap 4.3.9-3.7, php-ldap 4.3.9-3.7, php-odbc 4.3.9-3.7, php-pear 4.3.9-3.7, +7 more -
Red Hat Enterprise Linux 4 nmap Red Hat Enterprise Linux 5 nmapnot affected: vulnerable code not present
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.39% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 3.7 | AV:L/AC:H/Au:N/C:P/I:P/A:P |
References
-
debian.org
/security/2005/dsa-789
vendor-advisory
-
redhat.com
/support/errata/RHSA-2005-564.html
vendor-advisory
-
gentoo.org
/security/en/glsa/glsa-200506-08.xml
vendor-advisory
-
marc.info
/?l=bugtraq&m=111955937622637&w=2
vendor-advisory
-
zataz.net
/adviso/shtool-05252005.txt
vendor-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A9639
vdb-entry, signature
- bugs.gentoo.org /show_bug.cgi?id=93782
-
secunia.com
/advisories/15668
third-party-advisory
-
secunia.com
/advisories/15496
third-party-advisory
-
securitytracker.com
/id?1014059
vdb-entry
-
securityfocus.com
/bid/13767
vdb-entry
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A345
vdb-entry, signature
Sources
- CVE List CVE-2005-1751
- NVD CVE-2005-1751
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.