BIG-IP iRule Vulnerability
Summary
Description:
When an iRule that processes client traffic using the PEM::subscriber command is configured on a virtual server, undisclosed requests can cause the Traffic Management Microkernel (TMM) to terminate and may lead to remote code execution (RCE).
Impact:
Traffic is disrupted while...
Affected packages
| Package | Affected → Fixed | |
|---|---|---|
| F5BIG-IP |
≥ 21.1.0 (no fix yet)→ Not listed ≥ 17.5.0 (no fix yet)→ Not listed ≥ 17.1.0 (no fix yet)→ Not listed |
Not listed Not listed Not listed |
| F5BIG-IP Next for Kubernetes |
≥ 2.4.0 (no fix yet)→ Not listed ≥ 2.3.0 (no fix yet)→ Not listed ≥ 2.2.0 (no fix yet)→ Not listed |
Not listed Not listed Not listed |
| F5BIG-IP Next CNF |
≥ 2.4.0 (no fix yet)→ Not listed ≥ 2.3.0 (no fix yet)→ Not listed ≥ 2.2.0 (no fix yet)→ Not listed |
Not listed Not listed Not listed |
This record does not list fixed versions. Check the article or the vendor advisory in the references for whether and where it is fixed.
Original description The description as published by the source.
Description:
When an iRule that processes client traffic using the PEM::subscriber command is configured on a virtual server, undisclosed requests can cause the Traffic Management Microkernel (TMM) to terminate and may lead to remote code execution (RCE).
Impact:
Traffic is disrupted while the TMM process restarts. This vulnerability allows a remote unauthenticated attacker to cause a denial-of-service (DoS) on the BIG-IP system and may perform RCE. There is no control plane exposure; this is a data plane issue only.
Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
Source: CVE.org (CVE Program・cvelistV5) NVD
References
- web f5sirt@f5.com