Process crash via unpaired Exit node dereference
Published Nov 5, 2021 · Updated Aug 4, 2024
Null pointer dereference in TensorFlow before 2.4.4, 2.5.0 through 2.5.1, and 2.6.0 allows local users to crash the process. During control-flow graph construction, an Exit node without its paired Enter node leaves parent null, but the code dereferences parent to obtain a frame identifier. Exploitation requires low-privileged local execution of a malformed TensorFlow graph and interrupts only the hosting process.
Summary
What happened
Null pointer dereference in TensorFlow before 2.4.4, 2.5.0 through 2.5.1, and 2.6.0 allows local users to crash the process. During control-flow graph construction, an Exit node without its paired Enter node leaves parent null, but the code dereferences parent to obtain a frame identifier. Exploitation requires low-privileged local execution of a malformed TensorFlow graph and interrupts only the hosting process.
The record
- CVE
- CVE-2021-41217
- Published
- Nov 5, 2021
- Updated
- Aug 4, 2024
- Vendor
- Product
- TensorFlow
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 5, 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.4.4
- Affected versionversion=>= 2.5.0, < 2.5.2
- Affected versionversion=>= 2.6.0, < 2.6.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Upstream malformed Exit-node 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