dbcve.org
Big Ip Domain Name SystemApplication · F5

CVE-2022-41787

HIGH · 7.5 CVSS v3.1 Published 2022-10-19
Fix available
A fix is available. Upgrade to 13.1.5.1 / 14.1.5.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
In BIG-IP versions 17.0.x before 17.0.0.1, 16.1.x before 16.1.3.1, 15.1.x before 15.1.6.1, 14.1.x before 14.1.5.1, and 13.1.x before 13.1.5.1, when DNS profile is configured on a virtual server with DNS Express enabled, undisclosed DNS queries with DNSSEC can cause TMM to terminate.

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 DNS queries with DNSSEC to crash the TMM (Traffic Management Module) when a DNS profile with DNS Express is configured on a virtual server. This causes service interruption for all traffic processed by the affected TMM.

MitigationApply the vendor patches for affected versions: 17.0.0.1, 16.1.3.1, 15.1.6.1, 14.1.5.1, or 13.1.5.1 depending on the current deployed 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 Domain Name SystemApplication
Affected:>= 13.1.0, < 13.1.5.1>= 14.1.0, < 14.1.5.1>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.3.1>= 17.0.0, < 17.0.0.1
Big Ip Local Traffic ManagerApplication
Affected:>= 13.1.0, < 13.1.5.1>= 14.1.0, < 14.1.5.1>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.3.1>= 17.0.0, < 17.0.0.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 view /etc/oracle-release and compare the version number to the affected ranges: 13.1.0-13.1.5.0, 14.1.0-14.1.5.0, 15.1.0-15.1.6.0, 16.1.0-16.1.3.0, or 17.0.0
    Affected if The installed version falls within any of these ranges and the version is less than the fixed releases (13.1.5.1, 14.1.5.1, 15.1.6.1, 16.1.3.1, or 17.0.0.1)
  2. Identify DNS profiles configured on virtual servers
    Run 'tmsh list /ltm virtual all' and look for any virtual server that references a DNS profile in its properties
    Affected if Any virtual server has a DNS profile assigned
  3. Verify if DNS Express is enabled in the DNS profile
    For each DNS profile found, run 'tmsh list /ltm dns-profile <profile_name>' and check for 'dns-express' settings ordns-express enabled configuration
    Affected if The DNS profile has DNS Express enabled (records configured for DNS Express zone transfer)
  4. Confirm DNSSEC is active on the DNS profile
    In the same DNS profile configuration, check for 'dnssec' or 'validation' settings enabled
    Affected if DNSSEC validation is enabled on the DNS profile that also has DNS Express configured

The environment is affected if the BIG-IP version is within the vulnerable ranges AND a DNS profile with both DNS Express enabled and DNSSEC configured is attached to any virtual server.

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 13.1.5.1 / 14.1.5.1 / 15.1.6.1 or later
Fixed in 13.1.5.114.1.5.115.1.6.1
Interim mitigation

Apply the vendor patches for affected versions: 17.0.0.1, 16.1.3.1, 15.1.6.1, 14.1.5.1, or 13.1.5.1 depending on the current deployed version.

Recommended fix High confidence

Upgrade to 13.1.5.1, 14.1.5.1, 15.1.6.1, 16.1.3.1, or 17.0.0.1 (or later) depending on your current major version branch

  1. Identify affected BIG-IP modules (DNS or LTM with DNS profile configured) by reviewing virtual server configurations
  2. Confirm current version by running 'tmsh show /sys version' or checking in the web UI under Device > Overview
  3. Download the appropriate patched version from F5 Downloads (support.f5.com) based on your current major version: 13.1.5.1, 14.1.5.1, 15.1.6.1, 16.1.3.1, or 17.0.0.1
  4. Review F5 upgrade guidelines and create a backup/snapshot before proceeding
  5. Install the upgrade via ISO image or through the web UI (Device > Software Management > Image List > Install)
  6. Reboot the device if required by the upgrade process
  7. Verify the new version is running with 'tmsh show /sys version'
  8. Confirm DNS Express functionality is operational after upgrade
Caveat Standard F5 upgrade precautions apply - test in non-production environment first, backup configuration, and plan maintenance window

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
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
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,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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