Limited memory disclosure and corruption via sparse conversion
Published Feb 4, 2022 · Updated Apr 22, 2025
Out-of-bounds access in Google TensorFlow before 2.5.3, 2.6.0 through 2.6.2, and 2.7.0 allows attackers to read or write memory. TFLite's sparsity_format_converter.cc trusts malformed traversal-order and dimension-metadata indexes while expanding sparse tensors, indexing vectors without verifying their lengths. Exploitation requires an application to load an attacker-crafted TFLite model and grants limited reads and writes outside TFLite arrays within the processing context.
Summary
What happened
Out-of-bounds access in Google TensorFlow before 2.5.3, 2.6.0 through 2.6.2, and 2.7.0 allows attackers to read or write memory. TFLite's sparsity_format_converter.cc trusts malformed traversal-order and dimension-metadata indexes while expanding sparse tensors, indexing vectors without verifying their lengths. Exploitation requires an application to load an attacker-crafted TFLite model and grants limited reads and writes outside TFLite arrays within the processing context.
The record
- CVE
- CVE-2022-23560
- Published
- Feb 4, 2022
- Updated
- Apr 22, 2025
- Vendor
- Product
- TensorFlow
- Classifications
- CWE-125, CWE-787
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 4, 2022CVE publishedPublication date reported by the CVE source.
- Apr 22, 2025Record 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.5.3
- Affected versionversion=>= 2.6.0, < 2.6.3
- Affected versionversion=>= 2.7.0, < 2.7.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
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