IKE service interruption via buffer over-read
Published Apr 13, 2021 · Updated Aug 3, 2024
Out-of-bounds read in IKE in Wind River VxWorks 7 before 21.03 allows remote attackers to stop IKE-dependent services via a crafted packet. Public records identify the locus only as IKE: a malformed packet causes the implementation to read beyond a buffer boundary, but no function or field is disclosed. No authentication or user interaction is required, and the reported consequence is limited to interruption of IKE and services that depend on it.
Summary
What happened
Out-of-bounds read in IKE in Wind River VxWorks 7 before 21.03 allows remote attackers to stop IKE-dependent services via a crafted packet. Public records identify the locus only as IKE: a malformed packet causes the implementation to read beyond a buffer boundary, but no function or field is disclosed. No authentication or user interaction is required, and the reported consequence is limited to interruption of IKE and services that depend on it.
The record
- CVE
- CVE-2021-29997
- Published
- Apr 13, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 13, 2021CVE 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