tcpflow through 1.6.1 Out-of-Bounds Read via TCP Demultiplexer Payload Length
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
tcpflow, a tool for capturing and reconstructing TCP network traffic, is affected by this flaw. An unauthenticated attacker can send specially crafted network packets or inject them into captured traffic or pcap files to read memory the program should not access, potentially exposing sensitive data in the output files, or crash the tool.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
tcpflow through 1.6.1 contains an out-of-bounds read vulnerability that allows unauthenticated attackers to read process memory by sending packets with forged IP payload lengths. Attackers can inject crafted IPv4 or IPv6 TCP packets into captured traffic or pcap files to leak adjacent memory into reconstructed flow files or crash tcpflow.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- simsong tcpflow
through 1.6.1