| Gói / sản phẩm | Phiên bản bị ảnh hưởng | Phiên bản đã vá |
|---|---|---|
| big-ip access policy manager | ≥ 15.1.0, < 15.1.1≥ 16.0.0, < 16.0.1 | 15.1.116.0.1 |
| big-ip advanced firewall manager | ≥ 15.1.0, < 15.1.1≥ 16.0.0, < 16.0.1 | 15.1.116.0.1 |
| big-ip analytics | ≥ 15.1.0, < 15.1.1≥ 16.0.0, < 16.0.1 | 15.1.116.0.1 |
| big-ip application acceleration manager | ≥ 15.1.0, < 15.1.1≥ 16.0.0, < 16.0.1 | 15.1.116.0.1 |
| big-ip application security manager | ≥ 15.1.0, < 15.1.1≥ 16.0.0, < 16.0.1 | 15.1.116.0.1 |
| big-ip domain name system | ≥ 15.1.0, < 15.1.1≥ 16.0.0, < 16.0.1 | 15.1.116.0.1 |
| big-ip fraud protection service | ≥ 15.1.0, < 15.1.1≥ 16.0.0, < 16.0.1 | 15.1.116.0.1 |
| big-ip global traffic manager | ≥ 15.1.0, < 15.1.1≥ 16.0.0, < 16.0.1 | 15.1.116.0.1 |
| big-ip link controller | ≥ 15.1.0, < 15.1.1≥ 16.0.0, < 16.0.1 | 15.1.116.0.1 |
| big-ip local traffic manager | ≥ 15.1.0, < 15.1.1≥ 16.0.0, < 16.0.1 | 15.1.116.0.1 |
| big-ip policy enforcement manager | ≥ 15.1.0, < 15.1.1≥ 16.0.0, < 16.0.1 | 15.1.116.0.1 |
On BIG-IP versions 16.0.0-16.0.0.1 and 15.1.0-15.1.0.5, using the RESOLV::lookup command within an iRule may cause the Traffic Management Microkernel (TMM) to generate a core file and restart. This issue occurs when data exceeding the maximum limit of a hostname passes to the RESOLV::lookup command.
Bạn đang dùng một trong các sản phẩm này? Quét site để biết có đang lộ phiên bản có lỗ hổng không.
Quét site miễn phí