dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2022-35728

CRITICAL · 9.8 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 →
100/100
Remediation priority · Urgent
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 all versions of 13.1.x, and BIG-IQ version 8.x before 8.2.0 and all versions of 7.x, an authenticated user's iControl REST token may remain valid for a limited time after logging out from the Configuration utility. 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

iControl REST authentication tokens remain valid after a user logs out of the Configuration utility, allowing continued API access with stale tokens beyond the intended session lifecycle.

MitigationApply F5 security hotfixes (17.0.0.1, 16.1.3.1, 15.1.6.1, 14.1.5.1, 8.2.0) or upgrade to supported versions; monitor for suspicious post-logout API activity.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 F5 Big IP product version
    Run command 'tmsh show /sys version' or check the Configuration utility login page for version display
    Affected if The version displayed falls within any of these ranges: 13.1.0-13.1.5, 14.1.0-14.1.4, 15.1.0-15.1.5, 16.1.0-16.1.2, or exactly 17.0.0
  2. Confirm iControl REST is accessible
    Attempt to reach the iControl REST API endpoint at https://<management-ip>/mgmt/shared/authz or check that the REST API service is running via 'tmsh show /sys service restjavad'
    Affected if iControl REST API responds to requests, indicating the interface is enabled and accessible
  3. Verify the specific Big IP module in use
    Run 'tmsh show /sys module' or check System > Resource Provisioning in the Configuration utility to see which modules (APM, ASM, AFM, etc.) are provisioned
    Affected if Any of these modules are provisioned: APM, AFM, Analytics, AAM, ASM, DNS, FPS, GTM - all share the same vulnerable version ranges
  4. Check for active or lingering API sessions post-logout
    Review API access logs or invoke 'tmsh list /sys httpd' to inspect REST API authentication configuration
    Affected if Logs show API requests succeeding with tokens after the corresponding user session has logged out of the Configuration utility

Your environment is affected if the installed F5 Big IP version falls within the listed vulnerable ranges AND iControl REST is enabled and in use, regardless of which Big IP module is provisioned.

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

Apply F5 security hotfixes (17.0.0.1, 16.1.3.1, 15.1.6.1, 14.1.5.1, 8.2.0) or upgrade to supported versions; monitor for suspicious post-logout API activity.

Recommended fix High confidence

14.1.5.1, 15.1.6.1, 16.1.3.1, or 17.0.0.1 (or later)

  1. Identify the current BIG‑IP version (e.g., run 'tmsh show /sys version' or check the Configuration utility).
  2. Determine the appropriate target version based on your current branch: for 13.1.x upgrade to 14.1.5.1 or later; for 14.1.x upgrade to 14.1.5.1; for 15.1.x upgrade to 15.1.6.1; for 16.1.x upgrade to 16.1.3.1; for 17.0.x upgrade to 17.0.0.1.
  3. Review the F5 release notes for the chosen version to understand any breaking changes or required configuration adjustments.
  4. Perform a full configuration backup (e.g., via Configuration > Archive or 'tmsh save sys config').
  5. Schedule a maintenance window and upgrade the BIG‑IP device using the recommended upgrade procedure (ISO image, GUI, or tmsh).
  6. After upgrade, verify that the iControl REST token is no longer valid after logout by testing token reuse.
Caveat Upgrading across major version branches may introduce configuration or feature changes; review release notes and test in a staging environment before production deployment.

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
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
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,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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