Skip to content
Fencer Intel
high 7.5

CVE-2021-23039 json

On version 16.0.x before 16.0.1.2, 15.1.x before 15.1.3, 14.1.x before 14.1.2.8, and all versions of 13.1.x and 12.1.x, when IPSec is confi…

published 5y ago modified 4mo ago also EUVD-2021-10157

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 61%
public exploits
0
none known

Summary

On version 16.0.x before 16.0.1.2, 15.1.x before 15.1.3, 14.1.x before 14.1.2.8, and all versions of 13.1.x and 12.1.x, when IPSec is configured on a BIG-IP system, undisclosed requests from an authorized remote (IPSec) peer, which already has a negotiated Security Association, can cause the Traffic Management Microkernel (TMM) to terminate. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Patch / fix

  • f5 big-ip_access_policy_manager 14.1.2.8, 15.1.3, 16.0.1.2
  • f5 big-ip_advanced_firewall_manager 14.1.2.8, 15.1.3, 16.0.1.2
  • f5 big-ip_analytics 14.1.2.8, 15.1.3, 16.0.1.2
  • f5 big-ip_application_acceleration_manager 14.1.2.8, 15.1.3, 16.0.1.2
  • f5 big-ip_application_security_manager 14.1.2.8, 15.1.3, 16.0.1.2
  • f5 big-ip_domain_name_system 14.1.2.8, 15.1.3, 16.0.1.2
  • f5 big-ip_fraud_protection_service 14.1.2.8, 15.1.3, 16.0.1.2
  • f5 big-ip_global_traffic_manager 14.1.2.8, 15.1.3, 16.0.1.2
  • f5 big-ip_link_controller 14.1.2.8, 15.1.3, 16.0.1.2
  • f5 big-ip_local_traffic_manager 14.1.2.8, 15.1.3, 16.0.1.2
  • f5 big-ip_policy_enforcement_manager 14.1.2.8, 15.1.3, 16.0.1.2

Is CVE-2021-23039 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.95% chance of exploitation in the next 30 days, higher than 61% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 7.1 AV:N/AC:M/Au:N/C:N/I:N/A:C

Affected products

  • n/a BIG-IP

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.