CVE-2022-41813

BIG-IP PEM and AFM TMUI, TMSH and iControl vulnerability CVE-2022-41813

MEDIUM
6.5
CVSS Score
Published: October 19, 2022 at 09:23 PM UTC
Updated: June 17, 2026 at 05:03 AM UTC
2 products affected across 1 vendorBig IP Advanced Firewall ManagerBig IP Policy Enforcement Manager

Using BIG-IP AFM & PEM by F5?

Get instant alerts when new vulnerabilities affect BIG-IP AFM & PEM - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.5
Exploit prediction
EPSS 0.7%
SSVC
No known exploit

Description

In versions 16.1.x before 16.1.3.1, 15.1.x before 15.1.6.1, 14.1.x before 14.1.5, and all versions of 13.1.x, when BIG-IP is provisioned with PEM or AFM module, an undisclosed input can cause Traffic Management Microkernel (TMM) to terminate.

Affected

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

13.1.0 ≤ v ≤ 13.1.513.1.0 ≤ v < 13.1.x*14.1.0 ≤ v < 14.1.514.1.x ≤ v < 14.1.515.1.0 ≤ v < 15.1.6.115.1.x ≤ v < 15.1.6.116.1.0 ≤ v < 16.1.3.116.1.x ≤ v < 16.1.3.113.1.014.1.x15.1.x16.1.x
Affected range stops below 13.1.x*, so it looks safe — our inference, not a vendor statement
Affected range stops below 14.1.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 15.1.6.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 16.1.3.1, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 17.0.0 (unaffected)
13.1.0 ≤ v ≤ 13.1.513.1.0 ≤ v < 13.1.x*14.1.0 ≤ v < 14.1.514.1.x ≤ v < 14.1.515.1.0 ≤ v < 15.1.6.115.1.x ≤ v < 15.1.6.116.1.0 ≤ v < 16.1.3.116.1.x ≤ v < 16.1.3.113.1.014.1.x15.1.x16.1.x
Affected range stops below 13.1.x*, so it looks safe — our inference, not a vendor statement
Affected range stops below 14.1.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 15.1.6.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 16.1.3.1, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 17.0.0 (unaffected)

Remediation

No guide yet

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

References (1)

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

6.5MEDIUMf5
Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-20

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