CVE-2018-5504

N/A
Published: March 22, 2018 at 06:00 PM UTC
Updated: June 17, 2026 at 02:00 AM UTC
25 products affected across 2 vendorsBig IP Access Policy ManagerBig IP Application Security ManagerBig IP Advanced Firewall Manager

Using BIG-IP (LTM, AAM, AFM, Analytics, APM, ASM, DNS, Edge Gateway, GTM, Link Controller, PEM, WebAccelerator, WebSafe) by F5 Networks, Inc.?

Get instant alerts when new vulnerabilities affect BIG-IP (LTM, AAM, AFM, Analytics, APM, ASM, DNS, Edge Gateway, GTM, Link Controller, PEM, WebAccelerator, WebSafe) - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 4%

Description

In some circumstances, the Traffic Management Microkernel (TMM) does not properly handle certain malformed Websockets requests/responses, which allows remote attackers to cause a denial-of-service (DoS) or possible remote code execution on the F5 BIG-IP system running versions 13.0.0 - 13.1.0.3 or 12.1.0 - 12.1.3.1.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

12.1.0 ≤ v < 12.1.3.213.0.0 ≤ v < 13.1.0.4
Affected range stops below 12.1.3.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 13.1.0.4, so it looks safe — our inference, not a vendor statement
12.1.0 ≤ v ≤ 12.1.3.213.0.0 ≤ v < 13.1.0.4
Affected range stops below 13.1.0.4, so it looks safe — our inference, not a vendor statement
12.1.0 ≤ v < 12.1.3.213.0.0 ≤ v < 13.1.0.4
Affected range stops below 12.1.3.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 13.1.0.4, so it looks safe — our inference, not a vendor statement
12.1.0 ≤ v < 12.1.3.213.0.0 ≤ v < 13.1.0.4
Affected range stops below 12.1.3.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 13.1.0.4, so it looks safe — our inference, not a vendor statement
12.1.0 ≤ v < 12.1.3.213.0.0 ≤ v < 13.1.0.4
Affected range stops below 12.1.3.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 13.1.0.4, so it looks safe — our inference, not a vendor statement
12.1.0 ≤ v < 12.1.3.213.0.0 ≤ v ≤ 13.1.0.4
Affected range stops below 12.1.3.2, so it looks safe — our inference, not a vendor statement
12.1.0 ≤ v < 12.1.3.213.0.0 ≤ v < 13.1.0.4
Affected range stops below 12.1.3.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 13.1.0.4, so it looks safe — our inference, not a vendor statement
12.1.0 ≤ v < 12.1.3.213.0.0 ≤ v < 13.1.0.4
Affected range stops below 12.1.3.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 13.1.0.4, so it looks safe — our inference, not a vendor statement
12.1.0 ≤ v < 12.1.3.213.0.0 ≤ v < 13.1.0.4
Affected range stops below 12.1.3.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 13.1.0.4, so it looks safe — our inference, not a vendor statement
12.1.0 ≤ v < 12.1.3.213.0.0 ≤ v < 13.1.0.412.1.0 - 12.1.3.113.0.0 - 13.1.0.3
Affected range stops below 12.1.3.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 13.1.0.4, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (2)

VDB Entryx_refsource_SECTRACKThird Party Advisory
http://www.securitytracker.com/id/1040558
x_refsource_CONFIRMVendor Advisory
https://support.f5.com/csp/article/K11718033

CVSS

Confidentiality
COMPLETE
Integrity
COMPLETE
Availability
COMPLETE
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card