dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2022-26071

HIGH · 7.5 CVSS v3.1 Published 2022-05-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
On F5 BIG-IP 16.1.x versions prior to 16.1.2.2, 15.1.x versions prior to 15.1.5.1, 14.1.x versions prior to 14.1.4.6, 13.1.x versions prior to 13.1.5, and all versions of 12.1.x and 11.6.x, a flaw in the way reply ICMP packets are limited in the Traffic Management Microkernel (TMM) allows an attacker to quickly scan open UDP ports. This flaw allows an off-path remote attacker to effectively bypass source port UDP randomization. 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

F5 BIG-IP's Traffic Management Microkernel (TMM) improperly limits ICMP reply packets, enabling remote attackers to bypass UDP source port randomization. This allows off-path attackers to perform rapid UDP port scanning and identify open services, facilitating further attacks.

MitigationApply F5 BIG-IP patches: upgrade to 16.1.2.2+, 15.1.5.1+, 14.1.4.6+, or 13.1.5+ as appropriate. Note that 12.1.x and 11.6.x are end-of-life and require upgrade to a supported version.

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 Access Policy ManagerApplication
Affected:= 11.6.1= 11.6.2= 11.6.3= 11.6.4= 11.6.5= 12.1.0= 12.1.1= 12.1.2= 12.1.3= 12.1.4= 12.1.5= 12.1.6
Big Ip Advanced Firewall ManagerApplication
Affected:= 11.6.1= 11.6.2= 11.6.3= 11.6.4= 11.6.5= 12.1.0= 12.1.1= 12.1.2= 12.1.3= 12.1.4= 12.1.5= 12.1.6
Big Ip AnalyticsApplication
Affected:= 11.6.1= 11.6.2= 11.6.3= 11.6.4= 11.6.5= 12.1.0= 12.1.1= 12.1.2= 12.1.3= 12.1.4= 12.1.5= 12.1.6
Big Ip Application Acceleration ManagerApplication
Affected:= 11.6.1= 11.6.2= 11.6.3= 11.6.4= 11.6.5= 12.1.0= 12.1.1= 12.1.2= 12.1.3= 12.1.4= 12.1.5= 12.1.6
Big Ip Application Security ManagerApplication
Affected:= 11.6.1= 11.6.2= 11.6.3= 11.6.4= 11.6.5= 12.1.0= 12.1.1= 12.1.2= 12.1.3= 12.1.4= 12.1.5= 12.1.6
Big Ip Domain Name SystemApplication
Affected:= 11.6.1= 11.6.2= 11.6.3= 11.6.4= 11.6.5= 12.1.0= 12.1.1= 12.1.2= 12.1.3= 12.1.4= 12.1.5= 12.1.6
Big Ip Fraud Protection ServiceApplication
Affected:= 11.6.1= 11.6.2= 11.6.3= 11.6.4= 11.6.5= 12.1.0= 12.1.1= 12.1.2= 12.1.3= 12.1.4= 12.1.5= 12.1.6
Big Ip Global Traffic ManagerApplication
Affected:= 11.6.1= 11.6.2= 11.6.3= 11.6.4= 11.6.5= 12.1.0= 12.1.1= 12.1.2= 12.1.3= 12.1.4= 12.1.5= 12.1.6

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
High
Availability
None

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

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. Identify F5 BIG-IP product module
    Run 'tmsh show sys module' or check the BIG-IP UI for installed modules such as APM, AFM, Analytics, AAM, ASM, DNS, FPS, or GTM
    Affected if Any of these modules are installed and the version matches affected ranges
  2. Check BIG-IP version
    Run 'tmsh show sys version' or view the system information in the BIG-IP configuration utility
    Affected if Version is 11.6.1, 11.6.2, 11.6.3, 11.6.4, 11.6.5, 12.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.4, 12.1.5, or 12.1.6
  3. Verify TMM is active
    Run 'tmsh show sys tmm-info' to confirm the Traffic Management Microkernel is running and processing traffic
    Affected if TMM is active and handling traffic
  4. Confirm UDP services are exposed
    Review network configuration for any UDP-based services (DNS, syslog, etc.) exposed externally or to untrusted networks
    Affected if UDP services are reachable from untrusted networks

You are affected if you are running any F5 BIG-IP module (APM, AFM, Analytics, AAM, ASM, DNS, FPS, or GTM) at versions 11.6.1-11.6.5 or 12.1.0-12.1.6 with TMM active and UDP services exposed to untrusted networks.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply F5 BIG-IP patches: upgrade to 16.1.2.2+, 15.1.5.1+, 14.1.4.6+, or 13.1.5+ as appropriate. Note that 12.1.x and 11.6.x are end-of-life and require upgrade to a supported version.

Recommended fix High confidence

Upgrade to BIG-IP 16.1.2.2 or later, 15.1.5.1 or later, 14.1.4.6 or later, or 13.1.5 or later. Note: 11.6.x and 12.1.x versions are End of Technical Support (EoTS) and do not receive fixes; migration to a supported version is required.

  1. 1. Identify the current BIG-IP version by running 'tmsh show sys version' or checking the web UI at System > Software > Image List
  2. 2. Download the appropriate fixed version from the F5 downloads portal based on your major version line: 16.1.2.2 or later, 15.1.5.1 or later, 14.1.4.6 or later, or 13.1.5 or later
  3. 3. Prior to upgrading, review the release notes for the target version for any compatibility concerns
  4. 4. Upload the ISO image to the BIG-IP via the web UI (System > Software > Image List) or via tmsh: 'tmsh install sys software image <image-name> volume <volume-name>'
  5. 5. Install the new software version: 'tmsh install sys software volume <volume-name> <image-name>'
  6. 6. Reboot the system to activate the new version: 'tmsh reboot'
  7. 7. After reboot, verify the version is correct: 'tmsh show sys version'
  8. 8. Confirm the vulnerability is resolved by verifying ICMP rate limiting behavior and UDP port scan resistance
Caveat Upgrading across major version branches (e.g., 11.6.x to 15.x/16.x) may require configuration review and compatibility testing. Review F5 migration guides and consider testing in a staging environment before production deployment.

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

Fix this in Big Ip Access Policy Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-26071 — 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-2022-26071 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