CVE intelligence and bounded remediation

CVE-2016-6637 — Cloudfoundry Cloud Foundry Uaa Bosh security vulnerability

Critical CVSS 9.6

Multiple cross-site request forgery (CSRF) vulnerabilities in Pivotal Cloud Foundry (PCF) before 242; UAA 2.x before 2.7.4.7, 3.x before 3.3.0.5, and 3.4.x before 3.4.4; UAA BOSH before 11.5 and 12.x before 12.5; Elastic Runtime before 1.6.40, 1.7.x before 1.7.21, and 1.8.x before 1.8.2; and Ops Manager 1.7.x before 1.7.13 and 1.8.x before 1.8.1 allow remote attackers to hijack the authentication of unspecified victims for requests that approve or deny a scope via a profile or authorize approval page.

Severity
Critical
CVSS
9.6 (3.0)
Published
2016-09-30
CISA KEV
Not currently listed
Ecosystem
software/application
Weaknesses
CWE-352

Affected products

  • cloudfoundry / cloud_foundry_uaa_bosh
  • pivotal_software / cloud_foundry
  • pivotal_software / cloud_foundry_elastic_runtime / 1.6.0
  • pivotal_software / cloud_foundry_elastic_runtime / 1.6.1
  • pivotal_software / cloud_foundry_elastic_runtime / 1.6.2
  • pivotal_software / cloud_foundry_elastic_runtime / 1.6.3

Showing 6 representative product identities from 97 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

General vulnerability remediation

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Confirm the affected component, deployment paths, reachable interfaces, and enabled features from inventories and configuration, without probing production destructively.
  • Compare the advisory's affected conditions with the repository lockfiles, build manifests, artifacts, and runtime inventory.
  • Identify data sensitivity, trust boundaries, and privilege level for every confirmed affected deployment.

Remediate safely

  • Apply a vendor-supported fix or remove the affected component or feature; record the selected change and its source in the repository.
  • Update direct and transitive dependency locks, generated artifacts, deployment manifests, and asset inventories together.
  • Add a regression test for the documented unsafe condition using inert inputs and preserve rollback instructions.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.