Memory disclosure via in-place state patching
Published Dec 26, 2021 · Updated Aug 4, 2024
Use-after-free in the tremor-script crate before 0.11.6 allows attackers to disclose freed memory through a crafted patch expression. The in-place patch optimization can retain borrowed event strings in state after the event's backing byte array is freed, exposing stale or reallocated memory. Exploitation requires a Tremor script to patch state with event-referenced keys or values and assign the result back to state.
Summary
What happened
Use-after-free in the tremor-script crate before 0.11.6 allows attackers to disclose freed memory through a crafted patch expression. The in-place patch optimization can retain borrowed event strings in state after the event's backing byte array is freed, exposing stale or reallocated memory. Exploitation requires a Tremor script to patch state with event-referenced keys or values and assign the result back to state.
The record
- CVE
- CVE-2021-45701
- Published
- Dec 26, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 26, 2021CVE 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