Out of bounds access in tensorflow-lite
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `output_data` buffer. This might result in a segmentation fault but it can also be used to further corrupt the memory and can be chained with other vulnerabilities to create more advanced exploits. The issue is patched in commit 204945b19e44b57906c9344c0d00120eeeae178a and is released in TensorFlow versions 2.2.1, or 2.3.1. A potential workaround would be to add a custom `Verifier` to the model loading code to ensure that the segment ids are all positive, although this only handles the case when the segment ids are stored statically in the model. A similar validation could be done if the segment ids are generated at runtime between inference steps. If the segment ids are generated as outputs of a tensor during inference steps, then there are no possible workaround and users are advised to upgrade to patched code.
- Published
- Sep 25, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.7% · 53th percentile
- CWE
- CWE-787
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
34
Monitor
Low priority for now.
- CVSS
- 34 / 40 · 8.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CNA vs NVD score
- NVD
- 8.6
- CNA · GitHub_M
- 8.1
- 0.5 point gap
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| tensorflow | cpe:2.3:a:google:tensorflow |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- google tensorflow2.2.0 and later · before 2.2.1
- google tensorflow2.3.0 and later · before 2.3.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
tensorflow tensorflow
- >= 2.2.0, < 2.2.1, >= 2.3.0, < 2.3.1affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| PyPI | tensorflow | from 2.2.0 · before 2.2.1 | 2.2.1 |
| PyPI | tensorflow | from 2.3.0 · before 2.3.1 | 2.3.1 |
| PyPI | tensorflow-cpu | from 2.2.0 · before 2.2.1 | 2.2.1 |
| PyPI | tensorflow-cpu | from 2.3.0 · before 2.3.1 | 2.3.1 |
| PyPI | tensorflow-gpu | from 2.2.0 · before 2.2.1 | 2.2.1 |
| PyPI | tensorflow-gpu | from 2.3.0 · before 2.3.1 | 2.3.1 |
Same product
google: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-25668TensorFlow vulnerable to heap out-of-buffer read in the QuantizeAndDequantize operation39Monitor
- CVE-2023-25664TensorFlow vulnerable to Heap Buffer Overflow in AvgPoolGrad39Monitor
- CVE-2022-41900FractionalMaxPool and FractionalAVGPool heap out-of-bounds acess in Tensorflow39Monitor
- CVE-2022-35939Out of bounds write in `scatter_nd` op in TensorFlow Lite39Monitor
- CVE-2022-23587Integer overflow in Tensorflow39Monitor
- CVE-2020-15208Data corruption in tensorflow-lite39Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| PyPI:tensorflow | 2.2.1 | Package registry (OSV) |
| PyPI:tensorflow | 2.3.1 | Package registry (OSV) |
| PyPI:tensorflow-cpu | 2.2.1 | Package registry (OSV) |
| PyPI:tensorflow-cpu | 2.3.1 | Package registry (OSV) |
| PyPI:tensorflow-gpu | 2.2.1 | Package registry (OSV) |
| PyPI:tensorflow-gpu | 2.3.1 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- High
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- github.com/tensorflow/tensorflow/commit/204945b19e44b57906c9344c0d00120eeeae178a
- github.com/tensorflow/tensorflow/releases/tag/v2.3.1
Vendor advisories and official records. Exploit/PoC links are deliberately left out.