Security readout for executives and security teams
Plain-English summary
Affected Cloud Foundry Windows Stemcells on Google Cloud allowed containerized apps to reach the cloud metadata endpoint. That endpoint can expose privileged credentials. The main business risk is a malicious or compromised app developer using the app runtime to obtain credentials outside the app’s intended scope.
Executive priority
Prioritize remediation if the organization ran Cloud Foundry Windows workloads on Google Cloud before version 1200.14. Credential exposure can create impact beyond the vulnerable container, but available sources do not prove active exploitation.
Technical view
CVE-2018-1197 affects Windows Stemcells before 1200.14 when running containers on Google Cloud Platform. The issue is metadata endpoint exposure from inside Windows containers, enabling access to privileged credentials. The source bundle does not provide CVSS, CWE, exploit details, or broader platform impact.
Likely exposure
Exposure appears limited to deployments using Windows Stemcells prior to 1200.14 on Google Cloud Platform. The provided sources do not identify Linux stemcells, other clouds, or unrelated Windows container platforms as affected.
Exploitation context
The bundle does not show CISA KEV listing or public active exploitation evidence. The described threat actor is a malicious developer with an app running inside an affected Windows container, using unintended metadata endpoint access to obtain privileged credentials.
Researcher notes
Key missing details include CVSS scoring, exact metadata controls, credential scope, and exploit prerequisites beyond app execution inside affected containers. Analysis should stay bounded to Windows Stemcells before 1200.14 on GCP unless additional vendor evidence expands scope.
Mitigation direction
- Upgrade affected Windows Stemcells to version 1200.14 or later.
- Check the Cloud Foundry advisory for deployment-specific guidance.
- Inventory Windows Stemcell deployments running on Google Cloud Platform.
- Review and rotate credentials if untrusted apps ran before remediation.
Validation and detection
- Confirm Windows Stemcell versions are 1200.14 or later.
- Verify affected workloads ran on Google Cloud Platform, not only other environments.
- Review historical app tenancy for untrusted or compromised developers.
- Check cloud audit logs for suspicious credential use during the exposure window.
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.
CVE-2018-1197 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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 and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://www.cloudfoundry.org/blog/cve-2018-1197/CVE reference · x_refsource_CONFIRM
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.