ncurses exposes uninitialized memory in string reading functions
Priority LOW 38CWE-125Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- No fix listed
No CVSS vector from any source. Fix status from GitHub.
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.
Why it matters now
Fix No fix listed No fixed version in the sources yet
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | ncurses (crates.io) | up to 6.0.1 | — | No fix listed | GHSA-x77x-7mmh-cxv3 |
- ncurses (crates.io) Vendor— Affected up to 6.0.1 Fixed in — No fix listed GHSA-x77x-7mmh-cxv3
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-03 Threatist record created from GHSA-x77x-7mmh-cxv3
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences