Availability loss via crafted IKE packet
Published Mar 29, 2022 · Updated Aug 3, 2024
Out-of-bounds read in Wind River VxWorks 6.9 and 7 allows remote attackers to cause availability loss via a crafted IKE packet. During an IKE initial exchange, processing the packet reads beyond the intended memory boundary; public records do not identify the malformed field or responsible function. The IKE endpoint must be network-reachable, but no authentication or user interaction is required; only availability impact is reported.
Summary
What happened
Out-of-bounds read in Wind River VxWorks 6.9 and 7 allows remote attackers to cause availability loss via a crafted IKE packet. During an IKE initial exchange, processing the packet reads beyond the intended memory boundary; public records do not identify the malformed field or responsible function. The IKE endpoint must be network-reachable, but no authentication or user interaction is required; only availability impact is reported.
The record
- CVE
- CVE-2022-23937
- Published
- Mar 29, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 29, 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.
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