| Package | Affected versions | Patched versions |
|---|---|---|
| big-ip access policy manager | = 12.1.1≥ 12.1.2, < 12.1.4.1≥ 13.0.0, < 13.1.1.4≥ 14.0.0, < 14.1.0.2 | 12.1.4.113.1.1.414.1.0.2 |
| big-ip advanced firewall manager | = 12.1.1≥ 12.1.2, < 12.1.4.1≥ 13.0.0, < 13.1.1.4≥ 14.0.0, < 14.1.0.2 | 12.1.4.113.1.1.414.1.0.2 |
| big-ip analytics | = 12.1.1≥ 12.1.2, < 12.1.4.1≥ 13.0.0, < 13.1.1.4≥ 14.0.0, < 14.1.0.2 | 12.1.4.113.1.1.414.1.0.2 |
| big-ip application acceleration manager | = 12.1.1≥ 12.1.2, < 12.1.4.1≥ 13.0.0, < 13.1.1.4≥ 14.0.0, < 14.1.0.2 | 12.1.4.113.1.1.414.1.0.2 |
| big-ip application security manager | = 12.1.1≥ 12.1.2, < 12.1.4.1≥ 13.0.0, < 13.1.1.4≥ 14.0.0, < 14.1.0.2 | 12.1.4.113.1.1.414.1.0.2 |
| big-ip domain name system | = 12.1.1≥ 12.1.2, < 12.1.4.1≥ 13.0.0, < 13.1.1.4≥ 14.0.0, < 14.1.0.2 | 12.1.4.113.1.1.414.1.0.2 |
| big-ip edge gateway | = 12.1.1≥ 12.1.2, < 12.1.4.1≥ 13.0.0, < 13.1.1.4≥ 14.0.0, < 14.1.0.2 | 12.1.4.113.1.1.414.1.0.2 |
| big-ip fraud protection service | = 12.1.1≥ 12.1.2, < 12.1.4.1≥ 13.0.0, < 13.1.1.4≥ 14.0.0, < 14.1.0.2 | 12.1.4.113.1.1.414.1.0.2 |
| big-ip global traffic manager | = 12.1.1≥ 12.1.2, < 12.1.4.1≥ 13.0.0, < 13.1.1.4≥ 14.0.0, < 14.1.0.2 | 12.1.4.113.1.1.414.1.0.2 |
| big-ip link controller | = 12.1.1≥ 12.1.2, < 12.1.4.1≥ 13.0.0, < 13.1.1.4≥ 14.0.0, < 14.1.0.2 | 12.1.4.113.1.1.414.1.0.2 |
| big-ip local traffic manager | = 12.1.1≥ 12.1.2, < 12.1.4.1≥ 13.0.0, < 13.1.1.4≥ 14.0.0, < 14.1.0.2 | 12.1.4.113.1.1.414.1.0.2 |
| big-ip policy enforcement manager | = 12.1.1≥ 12.1.2, < 12.1.4.1≥ 13.0.0, < 13.1.1.4≥ 14.0.0, < 14.1.0.2 | 12.1.4.113.1.1.414.1.0.2 |
| big-ip webaccelerator | ≥ 12.1.2, < 12.1.4.1≥ 13.0.0, < 13.1.1.4≥ 14.0.0, < 14.1.0.2 | 12.1.4.113.1.1.414.1.0.2 |
| big-ip webaccelerator12.1.1 | = hf2 |
Platform dependent weakness. This issue only impacts iSeries platforms. On these platforms, in BIG-IP (LTM, AAM, AFM, Analytics, APM, ASM, DNS, Edge Gateway, FPS, GTM, Link Controller, PEM, WebAccelerator) versions 14.0.0-14.1.0.1, 13.0.0-13.1.1.3, and 12.1.1 HF2-12.1.4, the secureKeyCapable attribute was not set which causes secure vault to not use the F5 hardware support to store the unit key. Instead the unit key is stored in plaintext on disk as would be the case for Z100 systems. Additionally this causes the unit key to be stored in UCS files taken on these platforms.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free