Out-of-bounds read via unchecked VRRP checksum access
Published Aug 27, 2022 · Updated Dec 3, 2025
Buffer over-read in tcpdump before 4.9.3 allows remote attackers to trigger an out-of-bounds read with a crafted VRRPv3 packet. The vrrp_print() bad-checksum path reads the 16-bit checksum at bp[6] without first confirming that those bytes remain in the captured buffer. Reachability requires tcpdump to capture or open the malformed packet; the grounded code change establishes a memory over-read, not code execution.
Summary
What happened
Buffer over-read in tcpdump before 4.9.3 allows remote attackers to trigger an out-of-bounds read with a crafted VRRPv3 packet. The vrrp_print() bad-checksum path reads the 16-bit checksum at bp[6] without first confirming that those bytes remain in the captured buffer. Reachability requires tcpdump to capture or open the malformed packet; the grounded code change establishes a memory over-read, not code execution.
The record
- CVE
- CVE-2019-15167
- Published
- Aug 27, 2022
- Updated
- Dec 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 27, 2022CVE publishedPublication date reported by the CVE source.
- Dec 3, 2025Record 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Public exploit references
- Upstream VRRP buffer-overread regression captureproof 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