CVE-2017-6153
What it is
Features in F5 BIG-IP 13.0.0-13.1.0.3, 12.1.0-12.1.3.1, 11.6.1-11.6.3.1, 11.5.1-11.5.5, or 11.2.1 system that utilizes inflate functionality directly, via an iRule, or via the inflate code from PEM module are subjected to a service disruption via a "Zip Bomb" attack.
At a glance
- Exploitability
- Can be exploited over the network without logging in. Limited direct impact.
- Exploit odds
- 1.6% 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: 1.6% in the next 30 days (EPSS).
- Severity: 5.3 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 1.6% · EPSS, next 30 days
- Weakness
- CWE-400 · Uncontrolled resource consumption
- Record status
- Modified
Affected
- f5 big-ip Application Acceleration Manager ≤ 11.5.5
- f5 big-ip Application Acceleration Manager ≤ 11.6.3
- f5 big-ip Application Acceleration Manager ≤ 12.1.3
- f5 big-ip Application Acceleration Manager 11.2.1
- f5 big-ip Application Acceleration Manager 13.0.0
- f5 big-ip Application Acceleration Manager 13.1.0
- f5 big-ip Local Traffic Manager ≤ 11.5.5
- f5 big-ip Local Traffic Manager ≤ 11.6.3
Attack profile CVSS 3.0 · 5.3
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- Low
Raw vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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-6153.md and follow it. Check whether this project is affected by CVE-2017-6153. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
