CVE-2016-9256
What it is
In F5 BIG-IP 12.1.0 through 12.1.2, permissions enforced by iControl can lag behind the actual permissions assigned to a user if the role_map is not reloaded between the time the permissions are changed and the time of the user's next request. This is a race condition that occurs rarely in normal usage; the typical period in which this is possible is limited to at most a few seconds after the permission change.
At a glance
- Exploitability
- Can be exploited over the network with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 1.0% 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.0% in the next 30 days (EPSS).
- Severity: 7.5 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 1.0% · EPSS, next 30 days
- Weakness
- CWE-362 · Race condition
- Record status
- Modified
Affected
- f5 big-ip Local Traffic Manager 12.0.0
- 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.0.0
- 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
Attack profile CVSS 3.0 · 7.5
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/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-9256.md and follow it. Check whether this project is affected by CVE-2016-9256. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.