CVE-2017-6156
What it is
When the F5 BIG-IP 12.1.0-12.1.1, 11.6.0-11.6.1, 11.5.1-11.5.5, or 11.2.1 system is configured with a wildcard IPSec tunnel endpoint, it may allow a remote attacker to disrupt or impersonate the tunnels that have completed phase 1 IPSec negotiations. The attacker must possess the necessary credentials to negotiate the phase 1 of the IPSec exchange to exploit this vulnerability; in many environment this limits the attack surface to other endpoints under the same administration.
At a glance
- Exploitability
- Can be exploited over the network with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.9% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.9% in the next 30 days (EPSS).
- Severity: 6.4 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.9% · EPSS, next 30 days
- Record status
- Modified
Affected
- f5 big-ip Local Traffic Manager ≤ 11.5.5
- f5 big-ip Local Traffic Manager ≤ 12.1.1
- f5 big-ip Local Traffic Manager 11.2.1
- f5 big-ip Local Traffic Manager 11.6.1
- f5 big-ip Application Acceleration Manager ≤ 11.5.5
- f5 big-ip Application Acceleration Manager ≤ 12.1.1
- f5 big-ip Application Acceleration Manager 11.2.1
- f5 big-ip Application Acceleration Manager 11.6.1
Attack profile CVSS 3.0 · 6.4
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- High
Raw vector
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2017-6156.md and follow it. Check whether this project is affected by CVE-2017-6156. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
