Process memory corruption via duplicate resource release
Published Aug 12, 2021 · Updated Aug 4, 2024
Use-after-free in Google TensorFlow before 2.3.4, 2.4.0 through 2.4.2, and 2.5.0 lets local users crash a process via crafted arguments. BoostedTreesCreateEnsemble decrements a reference-counted resource after failed initialization, but its unique_ptr then releases the same object again and cleanup accesses freed members. Exploitation requires local code execution able to invoke the raw operation with an invalid serialized ensemble and corrupts the calling process during cleanup.
Summary
What happened
Use-after-free in Google TensorFlow before 2.3.4, 2.4.0 through 2.4.2, and 2.5.0 lets local users crash a process via crafted arguments. BoostedTreesCreateEnsemble decrements a reference-counted resource after failed initialization, but its unique_ptr then releases the same object again and cleanup accesses freed members. Exploitation requires local code execution able to invoke the raw operation with an invalid serialized ensemble and corrupts the calling process during cleanup.
The record
- CVE
- CVE-2021-37652
- Published
- Aug 12, 2021
- Updated
- Aug 4, 2024
- Vendor
- Product
- TensorFlow
- Classifications
- CWE-416, CWE-415
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 12, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.3.4
- Affected versionversion=>= 2.4.0, < 2.4.3
- Affected versionversion=>= 2.5.0, < 2.5.1
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.
Public exploit references
- BoostedTreesCreateEnsemble use-after-free reproducerproof of concept · demonstrated
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