BIG-IP iRule vulnerability
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| F5 | BIG-IP | unknown |
|
||||||||||||
| F5 | BIG-IP Next for Kubernetes | unknown |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| F5 | Big-ip |
|
||||||||||||||||
| F5 | Big-ip Next For Kubernetes |
|
Vendor Workaround
None
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Link | Providers |
|---|---|
| https://my.f5.com/manage/s/article/K000163940 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
F5
F5 big-ip F5 big-ip Next For Kubernetes |
|
| Vendors & Products |
F5
F5 big-ip F5 big-ip Next For Kubernetes |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Description: When an HTTP profile and an iRule using the MR::message route command are 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 allow the attacker to 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. | |
| Title | BIG-IP iRule vulnerability | |
| Weaknesses | CWE-121 | |
| References |
| |
| Metrics |
cvssV3_1
|
Stack-based Buffer Overflow