dbcve.org
Big Ip Domain Name SystemApplication · F5

CVE-2022-33947

MEDIUM · 6.5 CVSS v3.1 Published 2022-08-04
Fix available
A fix is available. Upgrade to 14.1.5 / 15.1.6.1 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
In BIG-IP Versions 16.1.x before 16.1.3, 15.1.x before 15.1.6.1, 14.1.x before 14.1.5, and all versions of 13.1.x, a vulnerability exists in undisclosed pages of the BIG-IP DNS Traffic Management User Interface (TMUI) that allows an authenticated attacker with at least operator role privileges to cause the Tomcat process to restart and perform unauthorized DNS requests and operations through undisclosed requests. 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

In BIG-IP DNS TMUI, an authenticated attacker with at least operator role privileges can exploit undisclosed pages to cause Tomcat process restart and perform unauthorized DNS requests and operations. The vulnerability requires authentication and operator-level privileges, targeting the web-based management interface for DNS traffic management.

MitigationUpgrade BIG-IP to version 16.1.3 or later, 15.1.6.1 or later, or 14.1.5 or later. Versions of 13.1.x require upgrade as they are past EoTS and receive no patches.

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 Domain Name SystemApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.3

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 DNS version
    Run 'tmsh show sys version' or access the TMUI and navigate to System > Software Management > BIG-IP Version to view the installed version
    Affected if The installed version falls within 13.1.0-13.1.5, 14.1.0-14.1.4, 15.1.0-15.1.5, or 16.1.0-16.1.2
  2. Verify TMUI access and operator accounts
    In the TMUI, navigate to User Management > User List to review existing user accounts and their assigned roles
    Affected if Any account with operator role or higher exists and can access the TMUI
  3. Review Tomcat process restarts
    Check system logs via 'tmsh show sys log' or the TMUI under Logs > System for Tomcat restart events, particularly from the dns module
    Affected if Unexpected or unauthorized Tomcat restarts are observed, especially those originating from DNS management pages
  4. Audit DNS operations in logs
    Review DNS-specific logs via 'tmsh show ltm dns' or the TMUI DNS logs for unauthorized or unexpected DNS requests and zone operations
    Affected if DNS operations appear that were not initiated by legitimate administrators

The environment is likely affected if the BIG-IP DNS version is within the affected ranges AND the TMUI is accessible to users with operator-level privileges.

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 14.1.5 / 15.1.6.1 / 16.1.3 or later
Fixed in 14.1.515.1.6.116.1.3
Interim mitigation

Upgrade BIG-IP to version 16.1.3 or later, 15.1.6.1 or later, or 14.1.5 or later. Versions of 13.1.x require upgrade as they are past EoTS and receive no patches.

Recommended fix High confidence

Upgrade to BIG-IP 16.1.3 or later, 15.1.6.1 or later, or 14.1.5 or later. Note: 13.1.x has no fix available as it is End of Technical Support (EoTS).

  1. 1. Identify the current BIG-IP DNS TMUI version by navigating to System > Software Management > ISO Image or checking the version via TMSH: show sys version
  2. 2. Determine the appropriate upgrade path based on current version: for 16.1.x upgrade to 16.1.3 or later; for 15.1.x upgrade to 15.1.6.1 or later; for 14.1.x upgrade to 14.1.5 or later; for 13.1.x note that no fix is available as this version is End of Technical Support (EoTS)
  3. 3. Download the appropriate hotfix ISO from the F5 Downloads portal at https://downloads.f5.com/ or from the F5 Cloud Services portal
  4. 4. Upload the ISO image to the BIG-IP device via the Web UI (System > Software Management > ISO Image > Import) or via TMSH: install sys software volume
  5. 5. Create a new boot volume for the upgrade: sys software volume create <volume-name> image <iso-image-name>
  6. 6. Reboot the system to boot from the new volume: sys software volume <volume-name> boot
  7. 7. After upgrade, verify the version is correct: tmsh show sys version | grep Version
  8. 8. Confirm the fix is applied by checking the security advisory status at support.f5.com for CVE-2022-33947
Caveat Upgrading BIG-IP versions may introduce configuration or compatibility changes; review F5 release notes for breaking changes between versions before upgrading.

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

Fix this in Big Ip Domain Name System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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