Process crash via XLA RandomShuffle null dereference
Published Mar 24, 2023 · Updated Feb 19, 2025
Null pointer dereference in TensorFlow before 2.11.1 allows remote attackers to crash a consuming process through XLA-compiled RandomShuffle. The XLA path for tf.raw_ops.RandomShuffle accepts crafted scalar and seed parameters and then dereferences a null pointer during JIT compilation. Exploitation requires XLA JIT to be enabled and a consuming application to let remote attackers control the operation's arguments; the demonstrated consequence is a process crash.
Summary
What happened
Null pointer dereference in TensorFlow before 2.11.1 allows remote attackers to crash a consuming process through XLA-compiled RandomShuffle. The XLA path for tf.raw_ops.RandomShuffle accepts crafted scalar and seed parameters and then dereferences a null pointer during JIT compilation. Exploitation requires XLA JIT to be enabled and a consuming application to let remote attackers control the operation's arguments; the demonstrated consequence is a process crash.
The record
- CVE
- CVE-2023-25674
- Published
- Mar 24, 2023
- Updated
- Feb 19, 2025
- Vendor
- Product
- TensorFlow
- Classifications
- CWE-476, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 24, 2023CVE publishedPublication date reported by the CVE source.
- Feb 19, 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.11.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 RandomShuffle XLA crash 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