# CVE-2004-1453: Information disclosure in n/a

> Local attackers can exploit LD_DEBUG in setuid programs to leak sensitive symbol information, requiring glibc upgrades.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Feb 2005
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2004-1453, GHSA-j6cx-h236-3cg8, RHSA-2005:256

## What is CVE-2004-1453?

CVE-2004-1453 is a low-severity vulnerability in Gnu Glibc, published on 13 Feb 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2004-1453?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `glibc` | Red Hat:enterprise_linux:3::as | All versions | 0:2.3.2-95.33 |
| `glibc-common` | Red Hat:enterprise_linux:3::as | All versions | 0:2.3.2-95.33 |
| `glibc-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:2.3.2-95.33 |
| `glibc-debuginfo-common` | Red Hat:enterprise_linux:3::as | All versions | 0:2.3.2-95.33 |
| `glibc-devel` | Red Hat:enterprise_linux:3::as | All versions | 0:2.3.2-95.33 |
| `glibc-headers` | Red Hat:enterprise_linux:3::as | All versions | 0:2.3.2-95.33 |
| `glibc-profile` | Red Hat:enterprise_linux:3::as | All versions | 0:2.3.2-95.33 |
| `glibc-utils` | Red Hat:enterprise_linux:3::as | All versions | 0:2.3.2-95.33 |
| `nptl-devel` | Red Hat:enterprise_linux:3::as | All versions | 0:2.3.2-95.33 |
| `nscd` | Red Hat:enterprise_linux:3::as | All versions | 0:2.3.2-95.33 |
| `glibc` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.3.2-95.33 |
| `glibc-common` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.3.2-95.33 |
| `glibc-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.3.2-95.33 |
| `glibc-debuginfo-common` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.3.2-95.33 |
| `glibc-devel` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.3.2-95.33 |
| `glibc-headers` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.3.2-95.33 |
| `glibc-profile` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.3.2-95.33 |
| `glibc-utils` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.3.2-95.33 |
| `nptl-devel` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.3.2-95.33 |
| `nscd` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.3.2-95.33 |
| `glibc` | Red Hat:enterprise_linux:3::es | All versions | 0:2.3.2-95.33 |
| `glibc-common` | Red Hat:enterprise_linux:3::es | All versions | 0:2.3.2-95.33 |
| `glibc-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 0:2.3.2-95.33 |
| `glibc-debuginfo-common` | Red Hat:enterprise_linux:3::es | All versions | 0:2.3.2-95.33 |
| `glibc-devel` | Red Hat:enterprise_linux:3::es | All versions | 0:2.3.2-95.33 |
| `glibc-headers` | Red Hat:enterprise_linux:3::es | All versions | 0:2.3.2-95.33 |
| `glibc-profile` | Red Hat:enterprise_linux:3::es | All versions | 0:2.3.2-95.33 |
| `glibc-utils` | Red Hat:enterprise_linux:3::es | All versions | 0:2.3.2-95.33 |
| `nptl-devel` | Red Hat:enterprise_linux:3::es | All versions | 0:2.3.2-95.33 |
| `nscd` | Red Hat:enterprise_linux:3::es | All versions | 0:2.3.2-95.33 |
| `glibc` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.3.2-95.33 |
| `glibc-common` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.3.2-95.33 |
| `glibc-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.3.2-95.33 |
| `glibc-debuginfo-common` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.3.2-95.33 |
| `glibc-devel` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.3.2-95.33 |
| `glibc-headers` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.3.2-95.33 |
| `glibc-profile` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.3.2-95.33 |
| `glibc-utils` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.3.2-95.33 |
| `nptl-devel` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.3.2-95.33 |
| `nscd` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.3.2-95.33 |

Products: Gnu Glibc.

## How do I fix CVE-2004-1453?

Upgrade to a fixed version.

## Is CVE-2004-1453 being exploited?

There is no known exploitation of CVE-2004-1453 in the wild and no public exploit code.

## Other vulnerabilities in Gnu Glibc

- [CVE-2026-5450](https://insights.sbomify.com/CVE-2026-5450/): scanf %mc off-by-one heap buffer overflow (critical 9.8)
- [CVE-2023-25139](https://insights.sbomify.com/CVE-2023-25139/): Memory corruption in n/a (critical 9.8)
- [CVE-1999-0199](https://insights.sbomify.com/CVE-1999-0199/): Other in n/a (critical 9.8)
- [CVE-2019-1010022](https://insights.sbomify.com/CVE-2019-1010022/): Security feature bypass in glibc (critical 9.8)
- [CVE-2005-3590](https://insights.sbomify.com/CVE-2005-3590/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-1453 and fix it if it is affected.

What it is: CVE-2004-1453 is a low-severity vulnerability in Gnu Glibc, published on 13 Feb 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2004-1453 in the wild and no public exploit code.

Affected product: Gnu Glibc. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2004-1453/ (Markdown: https://insights.sbomify.com/CVE-2004-1453/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2004-1453
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2004-1453
- OSV: https://osv.dev/vulnerability/CVE-2004-1453

---
From sbomify Insights: https://insights.sbomify.com/CVE-2004-1453/
Summaries are generated and may contain mistakes; the official description above is the record.