LiveActive security incident?Get immediate response
CVE Record

CVE-2021-29615: Stack overflow in `ParseAttrValue` with nested tensors

TensorFlow is an end-to-end open source platform for machine learning. The implementation of `ParseAttrValue`(https://github.com/tensorflow/tensorflow/blob/c22d88d6ff33031aa113e48aa3fc9aa74ed79595/tensorflow/core/framework/attr_value_util.cc#L397-L453) can be tricked into stack overflow due to recursion by giving in a specially crafted input. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.

LowCVSS 2.5Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2021-29615 is a low-severity TensorFlow issue where specially crafted input can cause a stack overflow in attribute parsing. The documented impact is limited availability loss, not data theft or code execution. Organizations mainly need to find older TensorFlow deployments and move them to a fixed release line.

Executive priority

Treat as routine patch hygiene unless TensorFlow is exposed to untrusted local users or shared ML environments. It is not an emergency based on available evidence, but unsupported or stale TensorFlow installations should be upgraded during the next maintenance window.

Technical view

TensorFlow's ParseAttrValue implementation used recursive handling that could be driven into stack overflow with nested tensor input. The CVSS 3.1 score is 2.5 with local access, high attack complexity, low privileges, no user interaction, and low availability impact only.

Likely exposure

Exposure is most likely in ML applications, notebooks, services, or containers using TensorFlow versions before the patched 2.1.4, 2.2.3, 2.3.3, 2.4.2, or 2.5.0 releases. Risk depends on whether local or low-privileged users can supply crafted TensorFlow inputs.

Exploitation context

The source bundle does not indicate active exploitation, and the CVE is not listed as KEV. The advisory describes specially crafted input causing stack overflow, but the CVSS vector limits this to local, high-complexity, low-privilege availability impact.

Researcher notes

Focus review on TensorFlow ParseAttrValue behavior and environments accepting nested tensor attributes from untrusted sources. The public record supports denial-of-service analysis only. No source provided evidence of confidentiality impact, integrity impact, remote exploitation, or exploit availability.

Mitigation direction

  • Upgrade TensorFlow to 2.5.0 where possible.
  • For supported older branches, apply 2.4.2, 2.3.3, 2.2.3, or 2.1.4.
  • Check the TensorFlow advisory for branch-specific upgrade guidance.
  • Limit untrusted local input paths to TensorFlow parsers until patched.

Validation and detection

  • Inventory TensorFlow versions in applications, containers, notebooks, and build manifests.
  • Flag versions below 2.1.4, 2.2.3, 2.3.3, or 2.4.2.
  • Confirm upgraded environments report a fixed TensorFlow release.
  • Review whether local users can provide TensorFlow model or graph inputs.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-674: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-29615 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
2.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
2.5CVSS 3.1LowCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L11.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

2.5Low
CVSS 3.1 vector shape for CVE-2021-29615Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
tensorflowtensorflow< 2.1.4, >= 2.2.0, < 2.2.3, >= 2.3.0, < 2.3.3, >= 2.4.0, < 2.4.2Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-674 · source CWE mapping

Uncontrolled Recursion

Uncontrolled Recursion represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.