| Name | CVE-2004-1453 |
| Description | GNU glibc 2.3.4 before 2.3.4.20040619, 2.3.3 before 2.3.3.20040420, and 2.3.2 before 2.3.2-r10 does not restrict the use of LD_DEBUG for a setuid program, which allows local users to gain sensitive information, such as the list of symbols used by the program. |
| Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
| Debian Bugs | 272210 |
Vulnerable and fixed packages
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|
| glibc (PTS) | bullseye | 2.31-13+deb11u11 | fixed |
| bullseye (security) | 2.31-13+deb11u10 | fixed |
| bookworm | 2.36-9+deb12u9 | fixed |
| bookworm (security) | 2.36-9+deb12u7 | fixed |
| sid, trixie | 2.40-4 | fixed |
The information below is based on the following data on fixed versions.
| Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
|---|
| glibc | source | (unstable) | 2.3.5 | unimportant | | 272210 |
Notes
according to GOTO Masanori this is not a security problem
Jakub Jelinek confirms http://sources.redhat.com/ml/libc-hacker/2004-08/msg00059.html
Although not a real issue we should play safe with 2.3.5, where the code
was reorganized