dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2022-33962

MEDIUM · 6.7 CVSS v3.1 Published 2022-08-04
Fix available
A fix is available. Upgrade to 14.1.5.1 / 15.1.6.1 or later.
See remediation →
69/100
Remediation priority · Elevated
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 all versions of 13.1.x, certain iRules commands may allow an attacker to bypass the access control restrictions for a self IP address, regardless of the port lockdown settings. 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 · moderate confidence

This is an access control bypass vulnerability in F5 BIG-IP where certain iRules commands can circumvent access control restrictions for self IP addresses, bypassing port lockdown settings. iRules are Tcl-based scripts used for traffic manipulation in BIG-IP. An attacker with the ability to execute specific iRules could gain unauthorized access to self IP addresses regardless of configured port lockdown policies.

MitigationUpgrade BIG-IP to version 17.0.0.1, 16.1.3.1, 15.1.6.1, or 14.1.5.1 (or later). Review existing iRules for potentially exploitative commands and verify port lockdown configurations are properly set after patching.

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:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.1>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.3.1= 17.0.0
Big Ip Advanced Firewall ManagerApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.1>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.3.1= 17.0.0
Big Ip AnalyticsApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.1>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.3.1= 17.0.0
Big Ip Application Acceleration ManagerApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.1>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.3.1= 17.0.0
Big Ip Application Security ManagerApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.1>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.3.1= 17.0.0
Big Ip Domain Name SystemApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.1>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.3.1= 17.0.0
Big Ip Fraud Protection ServiceApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.1>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.3.1= 17.0.0
Big Ip Global Traffic ManagerApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.1>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.3.1= 17.0.0

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

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/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. Determine BIG-IP version
    Run `tmsh show version` or check the web UI under Dashboard > Overview > System > Software Version. Compare the installed version against the affected ranges: 13.1.0-13.1.5, 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
  2. Verify iRules are in use
    In the web UI, navigate to Local Traffic > iRules or run `tmsh list ltm rule` via CLI to list all defined iRules
    Affected if Any iRules exist in the configuration
  3. Identify self IP addresses with port lockdown
    Run `tmsh list net self` or check Network > Self IPs in the web UI. Note the port lockdown settings for each self IP
    Affected if Self IP addresses exist with port lockdown configured
  4. Review iRules for potentially exploitative commands
    Examine the content of deployed iRules (via `tmsh list ltm rule <rule_name>`) for commands that manipulate self IP traffic or access control, such as IP::remote_addr or access control related commands
    Affected if iRules contain commands that could interact with self IP addresses or bypass access controls

You are affected if your BIG-IP version is within 13.1.0-13.1.5, 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 AND you have iRules deployed that interact with self IP addresses or access control settings.

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.1 / 15.1.6.1 / 16.1.3.1 or later
Fixed in 14.1.5.115.1.6.116.1.3.1
Interim mitigation

Upgrade BIG-IP to version 17.0.0.1, 16.1.3.1, 15.1.6.1, or 14.1.5.1 (or later). Review existing iRules for potentially exploitative commands and verify port lockdown configurations are properly set after patching.

Recommended fix High confidence

Upgrade to 14.1.5.1+ (or 15.1.6.1+, 16.1.3.1+, or 17.0.0.1+ depending on your branch). Version 13.1.x is EoTS and requires moving to a newer branch.

  1. 1. Identify the current BIG-IP version by running `tmsh show sys version` or checking the web UI
  2. 2. Determine which major version branch you are on (13.1.x, 14.1.x, 15.1.x, 16.1.x, or 17.0.x)
  3. 3. If on version 13.1.x, note that this branch is End of Technical Support (EoTS) and you must upgrade to a newer branch (14.1.5.1 or later recommended)
  4. 4. For 14.1.x versions: Upgrade to version 14.1.5.1 or later
  5. 5. For 15.1.x versions: Upgrade to version 15.1.6.1 or later
  6. 6. For 16.1.x versions: Upgrade to version 16.1.3.1 or later
  7. 7. For 17.0.x versions: Upgrade to version 17.0.0.1 or later
  8. 8. Download the appropriate ISO/ISO images from the F5 downloads portal (support.f5.com)
Caveat Review F5 release notes for your target version for any configuration or behavior changes; major version upgrades (e.g., 13.1.x to 14.1.x) may require compatibility testing.

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
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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