Repeated actions via missing IPsec replay check
Published Feb 18, 2020 · Updated Aug 4, 2024
Packet replay in FreeBSD 12.0-RELEASE before 12.0-RELEASE-p13 allows man-in-the-middle attackers to repeat actions over IPsec. The kernel IPsec packet processor omits the anti-replay-window check, so it accepts and processes a previously captured packet again. Exploitation requires the ability to capture and inject IPsec traffic, and the repeated effect depends on the higher-level protocol in use.
Summary
What happened
Packet replay in FreeBSD 12.0-RELEASE before 12.0-RELEASE-p13 allows man-in-the-middle attackers to repeat actions over IPsec. The kernel IPsec packet processor omits the anti-replay-window check, so it accepts and processes a previously captured packet again. Exploitation requires the ability to capture and inject IPsec traffic, and the repeated effect depends on the higher-level protocol in use.
The record
- CVE
- CVE-2019-5613
- Published
- Feb 18, 2020
- Updated
- Aug 4, 2024
- Vendor
- The FreeBSD Project
- Product
- FreeBSD
- Classifications
- CWE-345, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 18, 2020CVE 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=12.0 before 12.0-RELEASE-p13
What conditions does exploitation require?
What is affected?
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
No public exploit references are available in this record.
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