Process abort via empty DrawBoundingBoxes image
Published May 14, 2021 · Updated Aug 3, 2024
Denial of service in Google TensorFlow before 2.1.4, 2.2.3, 2.3.3, and 2.4.2 allows local users to crash a process with an empty image. DrawBoundingBoxes derives a negative row clamp from the zero image height and validates it with a fatal CHECK_GE assertion instead of returning an operator error. Reachability requires control over the images argument, and successful exploitation aborts only the process executing the operator.
Summary
What happened
Denial of service in Google TensorFlow before 2.1.4, 2.2.3, 2.3.3, and 2.4.2 allows local users to crash a process with an empty image. DrawBoundingBoxes derives a negative row clamp from the zero image height and validates it with a fatal CHECK_GE assertion instead of returning an operator error. Reachability requires control over the images argument, and successful exploitation aborts only the process executing the operator.
The record
- CVE
- CVE-2021-29533
- Published
- May 14, 2021
- Updated
- Aug 3, 2024
- Vendor
- Product
- TensorFlow
- Classifications
- 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?
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.
Weakness, pattern, technique
Public exploit references
- Upstream DrawBoundingBoxes crash proof of conceptproof 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