dbcve.org
Big Ip Policy Enforcement ManagerApplication · F5

CVE-2024-23982

HIGH · 7.5 CVSS v3.1 Published 2024-02-14
Fix available
A fix is available. Upgrade to after 17.1.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
When a BIG-IP PEM classification profile is configured on a UDP virtual server, undisclosed requests can cause the Traffic Management Microkernel (TMM) to terminate. This issue affects classification engines using signatures released between 09-08-2022 and 02-16-2023. See the table in the F5 Security Advisory for a complete list of affected classification signature files.  NOTE: Software versions which have reached End of Technical Support (EoTS) are not evaluated

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A denial of service vulnerability in F5 BIG-IP allows specially crafted requests to crash the Traffic Management Microkernel (TMM) when a PEM classification profile is configured on a UDP virtual server. The vulnerability exists in classification engines using signature files released between September 2022 and February 2023.

MitigationUpdate classification signatures to versions released after February 16, 2023, or upgrade to a patched BIG-IP software version that addresses this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Big Ip Policy Enforcement ManagerApplication
Affected:>= 15.1.0, <= 15.1.10>= 16.1.0, <= 16.1.4>= 17.1.0, <= 17.1.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check BIG-IP software version
    Run 'tmsh show sys version' or access the web UI to view the system version under System > Software Management > ISO Image or System > Overview
    Affected if The installed version is 15.1.0-15.1.10, 16.1.0-16.1.4, or 17.1.0-17.1.1
  2. Identify UDP virtual servers
    Run 'tmsh list ltm virtual whereudp' or use the web UI under Local Traffic > Virtual Servers to list virtual servers and identify those with UDP profile type
    Affected if Any UDP virtual server exists in the configuration
  3. Verify PEM classification profile on UDP virtual server
    Run 'tmsh list ltm virtual <virtual_name>' for each UDP virtual server and look for a 'pem-classification-profile' or 'classification' configuration block within the virtual server settings
    Affected if A PEM classification profile is explicitly attached to a UDP virtual server
  4. Check classification signature file version
    Run 'tmsh show sys classification signatures' or access the classification signature database file directly to identify the signature set release date
    Affected if The classification signatures were released between September 2022 and February 2023 (before the February 16, 2023 patch)

The environment is affected if the BIG-IP version falls within the affected ranges, a UDP virtual server exists, a PEM classification profile is attached to that UDP virtual server, and the classification signatures in use were released between September 2022 and February 2023.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 17.1.1
Interim mitigation

Update classification signatures to versions released after February 16, 2023, or upgrade to a patched BIG-IP software version that addresses this vulnerability.

Recommended fix High confidence

15.1.11+ (15.1.x), 16.1.5+ (16.1.x), or 17.1.2+ (17.1.x)

  1. 1. Back up the BIG-IP configuration before making any changes
  2. 2. Identify all UDP virtual servers with PEM classification profiles enabled
  3. 3. Review the classification signature files in use (released between 09-08-2022 and 02-16-2023)
  4. 4. Upgrade BIG-IP to version 15.1.11 or later for 15.1.x installations
  5. 5. Upgrade BIG-IP to version 16.1.5 or later for 16.1.x installations
  6. 6. Upgrade BIG-IP to version 17.1.2 or later for 17.1.x installations
  7. 7. After upgrade, verify that TMM processes are running stable
  8. 8. Test that UDP virtual servers with PEM classification profiles handle traffic correctly
Caveat Verify that custom PEM classification signatures are compatible with the new signature format in the upgrade; test in staging before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Big Ip Policy Enforcement Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-23982 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-23982 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data