Local process crash via null SdcaOptimizer pointer
Published May 14, 2021 · Updated Aug 3, 2024
Null pointer dereference in TensorFlow 2.4.0 through 2.4.1 allows local users to trigger a process crash via malformed SdcaOptimizer inputs. The SdcaOptimizer kernel binds a reference to a null object because it fails to validate user-supplied arguments against the operation's required constraints. Exploitation requires local code execution that can invoke the raw operation; impact is a denial of service limited to the affected process.
Summary
What happened
Null pointer dereference in TensorFlow 2.4.0 through 2.4.1 allows local users to trigger a process crash via malformed SdcaOptimizer inputs. The SdcaOptimizer kernel binds a reference to a null object because it fails to validate user-supplied arguments against the operation's required constraints. Exploitation requires local code execution that can invoke the raw operation; impact is a denial of service limited to the affected process.
The record
- CVE
- CVE-2021-29572
- Published
- May 14, 2021
- Updated
- Aug 3, 2024
- Vendor
- Product
- TensorFlow
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 14, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.1.4
- Affected versionversion=>= 2.2.0, < 2.2.3
- Affected versionversion=>= 2.3.0, < 2.3.3
- Affected versionversion=>= 2.4.0, < 2.4.2
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
- GHSA-5gqf-456p-4836 proof of conceptproof of concept · unverified
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