CVE-2000-0959 json
glibc2 does not properly clear the LD_DEBUG_OUTPUT and LD_DEBUG environmental variables when a program is spawned from a setuid program, wh…
published 25y ago modified last mo. also EUVD-2000-0946
- cvss
- 1.2
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 23%
- public exploits
- 0
- none known
Summary
glibc2 does not properly clear the LD_DEBUG_OUTPUT and LD_DEBUG environmental variables when a program is spawned from a setuid program, which could allow local users to overwrite files via a symlink attack.
Is CVE-2000-0959 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.31% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-17).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 1.2 | AV:L/AC:H/Au:N/C:N/I:P/A:N |
Classification
- Technology feeds
References
-
securityfocus.com
/bid/1719
vdb-entry, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/5299
vdb-entry
-
securityfocus.com
/archive/1/85028
mailing-list
Sources
- CVE List CVE-2000-0959
- NVD CVE-2000-0959
Fencer Intel 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.