Security readout for executives and security teams
Plain-English summary
This TensorFlow flaw lets a local, low-privileged attacker trigger unsafe behavior in certain map operations. The public advisory rates it high because successful abuse could affect confidentiality, integrity, and availability of the TensorFlow process. The evidence points to affected TensorFlow versions, not broad remote internet exposure.
Executive priority
Prioritize remediation where TensorFlow runs in shared, multi-user, production, or sensitive-data environments. Standalone research environments with trusted users are lower urgency, but should still be upgraded during normal dependency maintenance.
Technical view
CVE-2021-37671 is a CWE-824 null pointer reference binding issue in TensorFlow `tf.raw_ops.Map*` and `tf.raw_ops.OrderedMap*` operations. The code checked ascending `indices` but did not verify that `indices` was non-empty. TensorFlow patched it in commit 532f5c5a and included fixes in 2.6.0, 2.5.1, 2.4.3, and 2.3.4.
Likely exposure
Exposure is most likely in ML workloads, notebooks, services, or batch jobs running TensorFlow before fixed releases, especially where lower-privileged users, supplied models, or supplied tensors can reach TensorFlow raw map operations.
Exploitation context
The CVSS vector is local, low complexity, low privilege, and no user interaction. The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Treat this as a serious local/workload-level risk, not a confirmed exploited-in-the-wild issue.
Researcher notes
The public description is specific to empty `indices` handling in TensorFlow map operations and references one patch commit. The bundle does not provide proof-of-concept details, exploit telemetry, or additional affected products. Avoid assuming remote exploitability without separate evidence.
Mitigation direction
- Upgrade TensorFlow to 2.6.0 or later where feasible.
- For older supported branches, use TensorFlow 2.5.1, 2.4.3, or 2.3.4.
- Pin dependency versions so vulnerable TensorFlow releases are not reintroduced.
- Restrict untrusted users, models, and tensors from shared TensorFlow execution environments.
- Check TensorFlow vendor guidance for branch-specific support constraints.
Validation and detection
- Inventory TensorFlow versions in applications, images, notebooks, and ML job environments.
- Compare findings against affected ranges: 2.5.0, 2.4.x before 2.4.3, and before 2.3.4.
- Verify dependency lockfiles and SBOMs reference fixed TensorFlow versions.
- Confirm shared ML platforms separate untrusted workloads from sensitive data and credentials.
- Review whether application paths expose raw map operations to untrusted inputs.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-824: 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 lookupCVE-2021-37671 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-qr82-2c78-4m8hCVE reference · x_refsource_CONFIRM
- https://github.com/tensorflow/tensorflow/commit/532f5c5a547126c634fefd43bbad1dc6417678acCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Access of Uninitialized Pointer
Access of Uninitialized Pointer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.