Menu

Star on GitHub · 3.2k

CVE-2016-6657

7.4 · HIGH

An open redirect vulnerability has been detected with some Pivotal Cloud Foundry Elastic Runtime components.

Published Dec 16, 2016CWE-601EPSS 1.05%

Overview

CVE-2016-6657 is a high-severity vulnerability. It was published on December 16, 2016 and has a CVSS 3.0 base score of 7.4 (HIGH).

This vulnerability has a CVSS 3.0 base score of 7.4, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

An open redirect vulnerability has been detected with some Pivotal Cloud Foundry Elastic Runtime components. Users of affected versions should apply the following mitigation: Upgrade PCF Elastic Runtime 1.8.x versions to 1.8.12 or later. Upgrade PCF Ops Manager 1.7.x versions to 1.7.18 or later and 1.8.x versions to 1.8.10 or later.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2016-6657?

CVE-2016-6657 is a high-severity vulnerability. It was published on December 16, 2016 and has a CVSS 3.0 base score of 7.4 (HIGH).

How severe is CVE-2016-6657?

This vulnerability has a CVSS 3.0 base score of 7.4, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2016-6657?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2016-6657?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2016-6657 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2016

View all