dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2022-29479

MEDIUM · 5.3 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 →
62/100
Remediation priority · Elevated
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 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, and F5 BIG-IQ Centralized Management all versions of 8.x and 7.x, when an IPv6 self IP address is configured and the ipv6.strictcompliance database key is enabled (disabled by default) on a BIG-IP system, undisclosed packets may cause decreased performance. 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

When an IPv6 self IP address is configured on F5 BIG-IP or BIG-IQ systems with the ipv6.strictcompliance database key enabled (disabled by default), the system experiences decreased performance when processing certain undisclosed IPv6 packets. The vulnerability is exploitable over the network without authentication.

MitigationDisable the ipv6.strictcompliance database key (set to disabled) or upgrade to a patched version (15.1.5.1+, 14.1.4.6+, 13.1.5+) to restore normal performance.

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

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

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 the installed BIG-IP version
    Run 'tmsh show sys version' or 'bigstart status' to retrieve the system version. Compare against the affected range: 11.6.1 through 12.1.6.
    Affected if The installed 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.
  2. Verify an IPv6 self IP address is configured
    Run 'tmsh list net self-addr' and examine the output for IPv6 addresses (containing colons). Alternatively, navigate to Network > Self IPs in the GUI and check for addresses in IPv6 format.
    Affected if Any self IP address uses IPv6 notation (such as ::1, fe80::, or a full IPv6 address).
  3. Check the ipv6.strictcompliance database key status
    Run 'tmsh list sys db ipv6.strictcompliance' to view the current value. The key is disabled by default.
    Affected if The value is set to 'enabled' (the vulnerability only triggers when strict compliance is enabled).

The system is affected only if it runs an affected version (11.6.1-12.1.6), has an IPv6 self IP configured, AND has the ipv6.strictcompliance key enabled.

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

Disable the ipv6.strictcompliance database key (set to disabled) or upgrade to a patched version (15.1.5.1+, 14.1.4.6+, 13.1.5+) to restore normal performance.

Recommended fix High confidence

For BIG-IP 15.1.x upgrade to 15.1.5.1 or later; For 14.1.x upgrade to 14.1.4.6 or later; For 13.1.x upgrade to 13.1.5 or later; Note: 11.6.x versions are End of Technical Support and no upgrade path available

  1. 1. Identify the current BIG-IP version by checking the system information in the web UI or via tmsh command: show /sys version
  2. 2. Determine if IPv6 self IP addresses are configured on the affected system
  3. 3. Check the current value of the ipv6.strictcompliance database key by running: tmsh list /sys db ipv6.strictcompliance
  4. 4. If ipv6.strictcompliance is enabled (value is 'true'), consider disabling it as a temporary mitigation by running: tmsh modify /sys db ipv6.strictcompliance value false
  5. 5. Plan for upgrade to a fixed version based on your current major version branch
  6. 6. Before upgrading, review the F5 release notes and ensure backup of the configuration
  7. 7. Perform the upgrade following F5 recommended procedures
Caveat Review F5 release notes for potential compatibility issues; 11.6.x has reached EoTS - consider migration to supported version

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
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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