Remote memory exhaustion via incomplete OpenSSL task cleanup
Published Feb 15, 2024 · Updated Mar 18, 2025
Memory leak in OpenSSL task cleanup in Wind River VxWorks 7 22.09 and 23.03 allows remote attackers to exhaust limited per-task memory. When a VxWorks task or POSIX thread that has used OpenSSL exits, its limited per-task allocation is not freed and remains consumed. The public record does not disclose the remote trigger for context termination; the bounded consequence is retained memory and eventual service interruption.
Summary
What happened
Memory leak in OpenSSL task cleanup in Wind River VxWorks 7 22.09 and 23.03 allows remote attackers to exhaust limited per-task memory. When a VxWorks task or POSIX thread that has used OpenSSL exits, its limited per-task allocation is not freed and remains consumed. The public record does not disclose the remote trigger for context termination; the bounded consequence is retained memory and eventual service interruption.
The record
- CVE
- CVE-2023-51787
- Published
- Feb 15, 2024
- Updated
- Mar 18, 2025
- Vendor
- Wind River
- Product
- VxWorks
- Classifications
- CWE-200, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 15, 2024CVE publishedPublication date reported by the CVE source.
- Mar 18, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=23.03
- Affected versionversion=7_22.09
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