Service crash via unreleased LazyPRM states
Published Jun 17, 2022 · Updated Aug 4, 2024
Memory leaks in LazyPRM.cpp in Open Motion Planning Library 1.5.0 allow attackers to exhaust memory by repeatedly running the planner. LazyPRM::solve clones states at allocation sites on lines 324, 343, and 368 after the final freeMemory call, so those allocations remain unreleased. Exploitation requires a consuming application to invoke the affected planner; accumulating leaked states can exhaust memory and crash the process.
Summary
What happened
Memory leaks in LazyPRM.cpp in Open Motion Planning Library 1.5.0 allow attackers to exhaust memory by repeatedly running the planner. LazyPRM::solve clones states at allocation sites on lines 324, 343, and 368 after the final freeMemory call, so those allocations remain unreleased. Exploitation requires a consuming application to invoke the affected planner; accumulating leaked states can exhaust memory and crash the process.
The record
- CVE
- CVE-2021-41490
- Published
- Jun 17, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 17, 2022CVE 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?
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
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