tic crash via unterminated termcap input
Published Sep 20, 2021 · Updated Aug 4, 2024
Heap buffer over-read in ncurses through 6.2-1 allows attackers to crash the tic utility via a malformed termcap entry. During termcap-to-terminfo conversion, _nc_captoinfo calls cvtchar without first ensuring that the input string has reached a valid terminator, causing a one-byte read beyond the heap buffer. The crafted file must be parsed by tic; the documented consequence is process termination rather than code execution.
Summary
What happened
Heap buffer over-read in ncurses through 6.2-1 allows attackers to crash the tic utility via a malformed termcap entry. During termcap-to-terminfo conversion, _nc_captoinfo calls cvtchar without first ensuring that the input string has reached a valid terminator, causing a one-byte read beyond the heap buffer. The crafted file must be parsed by tic; the documented consequence is process termination rather than code execution.
The record
- CVE
- CVE-2021-39537
- Published
- Sep 20, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 20, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- captoinfo.c heap-buffer-overflow reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo