CVE-2016-9245
What it is
In F5 BIG-IP systems 12.1.0 - 12.1.2, malicious requests made to virtual servers with an HTTP profile can cause the TMM to restart. The issue is exposed with BIG-IP APM profiles, regardless of settings. The issue is also exposed with the non-default "Normalize URI" configuration options used in iRules and/or BIG-IP LTM policies. An attacker may be able to disrupt traffic or cause the BIG-IP system to fail over to another device in the device group.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of service disruption.
- Exploit odds
- 1.4% 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.4% in the next 30 days (EPSS).
- Severity: 5.9 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 1.4% · EPSS, next 30 days
- Weakness
- CWE-284 · Improper access control
- Record status
- Modified
Affected
- f5 big-ip Local Traffic Manager 12.1.0
- f5 big-ip Local Traffic Manager 12.1.1
- f5 big-ip Local Traffic Manager 12.1.2
- f5 big-ip Application Acceleration Manager 12.1.0
- f5 big-ip Application Acceleration Manager 12.1.1
- f5 big-ip Application Acceleration Manager 12.1.2
- f5 big-ip Advanced Firewall Manager 12.1.0
- f5 big-ip Advanced Firewall Manager 12.1.1
Attack profile CVSS 3.0 · 5.9
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/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-2016-9245.md and follow it. Check whether this project is affected by CVE-2016-9245. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.