LiveActive security incident?Get immediate response
CVE Record

CVE-2018-7575: Google TensorFlow 1.7.x and earlier is affected by a Buffer Overflow vulnerability.

Google TensorFlow 1.7.x and earlier is affected by a Buffer Overflow vulnerability. The type of exploitation is context-dependent.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2018-7575 is a buffer overflow reported in Google TensorFlow 1.7.x and earlier. Business risk depends on where TensorFlow is used and whether it processes untrusted models, data, or artifacts. The provided sources do not include CVSS scoring, CPEs, or confirmed exploitation.

Executive priority

Prioritize discovery first. This is an old TensorFlow vulnerability with unknown severity in the provided record, but legacy ML systems processing untrusted artifacts could carry meaningful operational risk. Escalate remediation where TensorFlow is exposed to external or third-party inputs.

Technical view

The CVE describes a buffer overflow in TensorFlow 1.7.x and earlier, with exploitation described as context-dependent. The bundle provides no CWE, CVSS vector, affected CPE list, exploit details, or fixed version. Validation should focus on locating TensorFlow versions and reviewing the TensorFlow advisory.

Likely exposure

Likely exposure is limited to environments running TensorFlow 1.7.x or earlier. Higher-risk cases include ML pipelines, notebooks, services, or batch jobs that process untrusted model files, tensors, datasets, or serialized artifacts. The provided affected-product metadata is incomplete.

Exploitation context

The supplied data does not support a claim of active exploitation. KEV is false in the bundle, and no exploit source is cited. The record states exploitation is context-dependent, so practical risk depends on how TensorFlow is invoked and what inputs it receives.

Researcher notes

Evidence is sparse: no CVSS, CWE, CPEs, exploit status, or fixed version is included in the bundle. Avoid assuming affected package coordinates beyond TensorFlow 1.7.x and earlier. Use TFSA-2018-004 as the primary vendor reference for exact technical and remediation details.

Mitigation direction

  • Inventory TensorFlow installations and identify versions 1.7.x or earlier.
  • Review the TensorFlow TFSA-2018-004 advisory for vendor-specific remediation.
  • Upgrade to a vendor-supported fixed TensorFlow version if identified by the advisory.
  • Restrict untrusted model, dataset, or serialized artifact processing until remediated.
  • Isolate legacy TensorFlow workloads from sensitive systems and credentials.

Validation and detection

  • Search dependency manifests, containers, notebooks, and runtime images for TensorFlow versions.
  • Confirm whether any runtime uses TensorFlow 1.7.x or earlier.
  • Map affected workloads to data sources and trust boundaries.
  • Check whether workloads process third-party models, datasets, or serialized files.
  • Document compensating controls for any legacy TensorFlow workloads awaiting upgrade.
Prepared
Confidence
medium
Sources
3

Public sources used

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.

cve · low confidence lookup

CVE-2018-7575 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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