dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2022-35735

HIGH · 7.2 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 →
78/100
Remediation priority · High
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.1, 15.1.x before 15.1.6.1, 14.1.x before 14.1.5.1, and all versions of 13.1.x, an authenticated attacker with Resource Administrator or Manager privileges can create or modify existing monitor objects in the Configuration utility in an undisclosed manner leading to a privilege escalation. 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

Authenticated privilege escalation in F5 BIG-IP Configuration utility where attackers with Resource Administrator or Manager privileges can create or modify monitor objects in an undisclosed manner to elevate their permissions beyond their assigned role.

MitigationUpgrade BIG-IP to version 16.1.3.1, 15.1.6.1, 14.1.5.1 or later. Versions 13.1.x have no patch available and require migration to a supported 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 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
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
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
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
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
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
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
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

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

CVSS:3.1/AV:N/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. Identify the installed BIG-IP version
    Run 'tmsh show /sys version' on the command line, or log into the Configuration utility and check the version displayed on the login page or under System > Software Management > ISO Image
    Affected if The version is 13.1.0 through 13.1.5, 14.1.0 through 14.1.5.0, 15.1.0 through 15.1.6.0, or 16.1.0 through 16.1.3.0 (any version within the listed vulnerable ranges)
  2. Confirm the Configuration utility is accessible
    Verify the BIG-IP management web interface (Configuration utility) is reachable on port 443 or 8443, or check via 'tmsh list /sys httpd' to see if the management interface is enabled
    Affected if The Configuration utility is accessible over the network (this is required for the exploit to be usable)
  3. Check for users with Resource Administrator or Manager roles
    Run 'tmsh list /auth user' to list all local users and their assigned roles, or view users in the Configuration utility under User Management > User List
    Affected if Any user account possesses the Resource Administrator or Manager role in the BIG-IP system

You are affected if your BIG-IP version falls within the vulnerable ranges AND the Configuration utility is accessible AND you have users with Resource Administrator or Manager roles present in the system.

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 16.1.3.1, 15.1.6.1, 14.1.5.1 or later. Versions 13.1.x have no patch available and require migration to a supported version.

Recommended fix High confidence

16.1.3.1 (for 16.1.x), 15.1.6.1 (for 15.1.x), 14.1.5.1 (for 14.1.x); 13.1.x has no fix - upgrade to a supported version

  1. Identify the currently running Big-IP version (13.1.x, 14.1.x, 15.1.x, or 16.1.x)
  2. For Big-IP 16.1.x: Upgrade to version 16.1.3.1 or later
  3. For Big-IP 15.1.x: Upgrade to version 15.1.6.1 or later
  4. For Big-IP 14.1.x: Upgrade to version 14.1.5.1 or later
  5. For Big-IP 13.1.x: Note that this version line has no fixed version available; consider upgrading to a supported version line (14.1.x, 15.1.x, or 16.1.x)
  6. After upgrade, verify the version and ensure the Configuration utility is accessible
  7. Note: The attacker requires Resource Administrator or Manager privileges; review user access controls post-upgrade
Caveat Review F5 release notes for any configuration or compatibility changes between versions; 13.1.x reaches End of Technical Support - consider migrating to a supported version line

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
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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