F5 BIG-IP up to 15.1.0.4 Traffic Management Microkernel resource consumption

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in F5 BIG-IP up to 15.1.0.4. It has been classified as problematic. This affects an unknown part of the component Traffic Management Microkernel. Performing a manipulation results in resource consumption. This vulnerability is known as CVE-2020-5918. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability was found in F5 BIG-IP up to 15.1.0.4 (Firewall Software). It has been classified as problematic. This affects an unknown code block of the component Traffic Management Microkernel. The manipulation with an unknown input leads to a resource consumption vulnerability. CWE is classifying the issue as CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. This is going to have an impact on availability. The summary by CVE is:
In BIG-IP versions 15.1.0-15.1.0.4, 15.0.0-15.0.1.3, 14.1.0-14.1.2.3, 13.1.0-13.1.3.3, 12.1.0-12.1.5.1, and 11.6.1-11.6.5.1, the Traffic Management Microkernel (TMM) may stop responding when processing Stream Control Transmission Protocol (SCTP) traffic when traffic volume is high. This vulnerability affects TMM by way of a virtual server configured with an SCTP profile.
The weakness was published 08/26/2020 (Website). The advisory is shared at support.f5.com. This vulnerability is uniquely identified as CVE-2020-5918 since 01/06/2020. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/26/2020). MITRE ATT&CK project uses the attack technique T1499 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Similar entries are available at VDB-160308, VDB-160307, VDB-160303 and VDB-160302. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
- 11.6.5.0
- 11.6.5.1
- 12.1.5.0
- 12.1.5.1
- 13.1.3.0
- 13.1.3.1
- 13.1.3.2
- 13.1.3.3
- 14.1.2.0
- 14.1.2.1
- 14.1.2.2
- 14.1.2.3
- 15.0.1.0
- 15.0.1.1
- 15.0.1.2
- 15.0.1.3
- 15.1.0.0
- 15.1.0.1
- 15.1.0.2
- 15.1.0.3
- 15.1.0.4
License
Website
- Vendor: https://f5.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Resource consumptionCWE: CWE-400 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/06/2020 🔍08/26/2020 🔍
08/26/2020 🔍
08/26/2020 🔍
Sources
Vendor: f5.comAdvisory: support.f5.com
Status: Not defined
CVE: CVE-2020-5918 (🔍)
GCVE (CVE): GCVE-0-2020-5918
GCVE (VulDB): GCVE-100-160305
See also: 🔍
Entry
Created: 08/26/2020 20:52Updated: 08/26/2020 20:57
Changes: 08/26/2020 20:52 (38), 08/26/2020 20:57 (18)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.