GHSA-x77x-7mmh-cxv3 json
ncurses exposes uninitialized memory in string reading functions
published last yr. modified last yr. also RUSTSEC-2025-0108
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
Multiple string reading functions expose uninitialized memory by setting length to capacity when no null terminator is found.
This allows reading uninitialized memory which may contain sensitive data from previous allocations.
The ncurses-rs repository is archived and unmaintained.
Is GHSA-x77x-7mmh-cxv3 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | ncurses | <=6.0.1 >=0.0.0-0 |
no fix listed |
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
References
-
github.com
/RustSec/advisory-db/pull/2427
web
-
github.com
/jeaye/ncurses-rs
package
-
rustsec.org
/advisories/RUSTSEC-2025-0108.html
web, advisory
-
crates.io
/crates/ncurses
package
Sources
- GitHub Advisory GHSA-x77x-7mmh-cxv3
- OSV RUSTSEC-2025-0108
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.