Daemon crash via missing-state logger dereference
Published Jan 15, 2022 · Updated Aug 3, 2024
NULL pointer dereference in Libreswan 4.2 through 4.5 allows remote attackers to crash and restart the pluto daemon via malformed IKEv1 packets. The IKEv1 packet-processing path logs malformed payloads through st->st_logger even when early rejection leaves the state object null. Main Mode or Aggressive Mode traffic can reach the flaw without authentication, and repeated packets can keep the IKE service unavailable.
Summary
What happened
NULL pointer dereference in Libreswan 4.2 through 4.5 allows remote attackers to crash and restart the pluto daemon via malformed IKEv1 packets. The IKEv1 packet-processing path logs malformed payloads through st->st_logger even when early rejection leaves the state object null. Main Mode or Aggressive Mode traffic can reach the flaw without authentication, and repeated packets can keep the IKE service unavailable.
The record
- CVE
- CVE-2022-23094
- Published
- Jan 15, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 15, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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
- Malformed IKEv1 packet crash 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