dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2022-28706

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 and 15.1.x versions prior to 15.1.5.1, when the DNS resolver configuration is used, undisclosed requests can cause the Traffic Management Microkernel (TMM) to terminate. 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's DNS resolver allows remote attackers to cause the Traffic Management Microkernel (TMM) to terminate by sending undisclosed DNS requests. This affects BIG-IP 16.1.x before 16.1.2 and 15.1.x before 15.1.5.1, leading to service disruption.

MitigationUpgrade BIG-IP to version 16.1.2 or later, or 15.1.5.1 or later. If immediate patching is not possible, consider disabling or restricting access to the DNS resolver service as a temporary mitigation.

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:= 15.1.0= 15.1.1= 15.1.2= 15.1.3= 15.1.4= 15.1.5= 16.1.0= 16.1.1= 16.1.2
Big Ip Advanced Firewall ManagerApplication
Affected:= 15.1.0= 15.1.1= 15.1.2= 15.1.3= 15.1.4= 15.1.5= 16.1.0= 16.1.1= 16.1.2
Big Ip AnalyticsApplication
Affected:= 15.1.0= 15.1.1= 15.1.2= 15.1.3= 15.1.4= 15.1.5= 16.1.0= 16.1.1= 16.1.2
Big Ip Application Acceleration ManagerApplication
Affected:= 15.1.0= 15.1.1= 15.1.2= 15.1.3= 15.1.4= 15.1.5= 16.1.0= 16.1.1= 16.1.2
Big Ip Application Security ManagerApplication
Affected:= 15.1.0= 15.1.1= 15.1.2= 15.1.3= 15.1.4= 15.1.5= 16.1.0= 16.1.1= 16.1.2
Big Ip Domain Name SystemApplication
Affected:= 15.1.0= 15.1.1= 15.1.2= 15.1.3= 15.1.4= 15.1.5= 16.1.0= 16.1.1= 16.1.2
Big Ip Fraud Protection ServiceApplication
Affected:= 15.1.0= 15.1.1= 15.1.2= 15.1.3= 15.1.4= 15.1.5= 16.1.0= 16.1.1= 16.1.2
Big Ip Global Traffic ManagerApplication
Affected:= 15.1.0= 15.1.1= 15.1.2= 15.1.3= 15.1.4= 15.1.5= 16.1.0= 16.1.1= 16.1.2

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 version
    Run `tmsh show sys version` or `bigpipe version` from the command line to obtain the installed BIG-IP version
    Affected if The version is 15.1.0 through 15.1.5, or 16.1.0 through 16.1.2 (versions before 15.1.5.1 or 16.1.2)
  2. Verify DNS resolver is enabled
    Run `tmsh show ltm dns` or check the DNS profile configuration under Local Traffic > DNS > Profiles in the BIG-IP configuration
    Affected if A DNS resolver profile is active and processing DNS requests on the system
  3. Check TMM status
    Run `tmsh show sys tmm-info` to verify TMM is running; a crash would show in `tmsh show sys crashlog`
    Affected if TMM has recently restarted or crashed with DNS-related errors
  4. Confirm module versions
    Run `tmsh show sys software` to list installed modules and their versions
    Affected if Any BIG-IP module listed in the affected products (DNS, APM, AFM, AAM, ASM, Analytics, FPS, GTM) is present at a vulnerable version

You are affected if your BIG-IP runs version 15.1.0-15.1.5 or 16.1.0-16.1.2 and has the DNS resolver feature enabled and exposed to network traffic.

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

Upgrade BIG-IP to version 16.1.2 or later, or 15.1.5.1 or later. If immediate patching is not possible, consider disabling or restricting access to the DNS resolver service as a temporary mitigation.

Recommended fix High confidence

BIG-IP 15.1.5.1 or later (or 16.1.2+ if on 16.1.x branch)

  1. Identify the specific BIG-IP module(s) in use (APM, AFM, Analytics, AAM, ASM, DNS, FPS, or GTM)
  2. Confirm the currently installed version is 15.1.0, 15.1.1, 15.1.2, or 15.1.3
  3. Verify the DNS resolver feature is enabled in the configuration
  4. Schedule a maintenance window for the upgrade
  5. Download BIG-IP version 15.1.5.1 or later from the F5 Networks download portal (support.f5.com)
  6. Follow F5 upgrade documentation to apply the new version to all affected devices
  7. After upgrade, verify TMM processes are running normally
  8. Test DNS resolver functionality to confirm the vulnerability is remediated
Caveat Review F5 release notes for 15.1.5.1 for any configuration or behavioral changes; test in non-production environment first

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
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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