dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2022-41770

MEDIUM · 6.5 CVSS v3.1 Published 2022-10-19
Fix available
A fix is available. Upgrade to 14.1.5.1 / 15.1.7 or later.
See remediation →
71/100
Remediation priority · Elevated
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 17.0.x before 17.0.0.1, 16.1.x before 16.1.3.1, 15.1.x before 15.1.7, 14.1.x before 14.1.5.1, and all versions of 13.1.x, and BIG-IQ all versions of 8.x and 7.x, an authenticated iControl REST user can cause an increase in memory resource utilization, via undisclosed requests.

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

An authenticated iControl REST user can send specific requests that cause excessive memory consumption on BIG-IP and BIG-IQ devices, potentially leading to denial of service. This memory exhaustion vulnerability affects multiple version branches of BIG-IP (13.1.x, 14.1.x before 14.1.5.1, 15.1.x before 15.1.7, 16.1.x before 16.1.3.1, 17.0.x before 17.0.0.1) and all versions of BIG-IQ 7.x and 8.x.

MitigationApply the vendor-supplied patches (17.0.0.1, 16.1.3.1, 15.1.7, 14.1.5.1) to all affected BIG-IP and BIG-IQ systems. Since authentication is required, also review and limit iControl REST API access to only necessary administrative users.

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.7>= 16.1.0, < 16.1.3.1>= 17.0.0, < 17.0.0.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.7>= 16.1.0, < 16.1.3.1>= 17.0.0, < 17.0.0.1
Big Ip AnalyticsApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.1>= 15.1.0, < 15.1.7>= 16.1.0, < 16.1.3.1>= 17.0.0, < 17.0.0.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.7>= 16.1.0, < 16.1.3.1>= 17.0.0, < 17.0.0.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.7>= 16.1.0, < 16.1.3.1>= 17.0.0, < 17.0.0.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.7>= 16.1.0, < 16.1.3.1>= 17.0.0, < 17.0.0.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.7>= 16.1.0, < 16.1.3.1>= 17.0.0, < 17.0.0.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.7>= 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify the installed BIG-IP or BIG-IQ version
    Run 'tmsh show sys version' on the command line or query the iControl REST endpoint GET /mgmt/tm/sys/version. Alternatively, check the web UI login page footer which displays the version.
    Affected if The version falls within 13.1.0-13.1.5, 14.1.0-14.1.5.0, 15.1.0-15.1.6, 16.1.0-16.1.3.0, or 17.0.0 on BIG-IP, or any 7.x or 8.x version on BIG-IQ.
  2. Confirm iControl REST service is enabled
    Run 'tmsh show sys service restnoded' or query GET /mgmt/tm/sys/service/restnoded. The service must be running for the vulnerability to be exploitable.
    Affected if The iControl REST service (restnoded) is running and accessible.
  3. Verify iControl REST API is exposed
    Check the management interface accessibility by reviewing 'tmsh list sys httpd' output. Specifically look for 'manage-ingress' and 'rest-api' settings. Also review network access lists or firewall policies that allow access to port 443 on the management interface.
    Affected if The iControl REST API is reachable from network segments where untrusted users exist, or if admin credentials may be compromised.
  4. Review administrative user access to iControl REST
    Run 'tmsh list auth user' to enumerate users with administrative privileges, or query GET /mgmt/tm/auth/user. The vulnerability requires an authenticated user, so examine which users have iControl REST access.
    Affected if There are administrative or user accounts with iControl REST access, particularly if those accounts are used by automation tools or shared across systems.

Your environment is affected if you run a vulnerable BIG-IP version (13.1.0-13.1.5, 14.1.0-14.1.5.0, 15.1.0-15.1.6, 16.1.0-16.1.3.0, or 17.0.0) or any BIG-IQ 7.x/8.x version AND the iControl REST service is enabled and accessible to users who could send the malicious requests.

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

Apply the vendor-supplied patches (17.0.0.1, 16.1.3.1, 15.1.7, 14.1.5.1) to all affected BIG-IP and BIG-IQ systems. Since authentication is required, also review and limit iControl REST API access to only necessary administrative users.

Recommended fix High confidence

Upgrade to the fixed version in your current branch: 14.1.5.1, 15.1.7, or 16.1.3.1 (13.1.x has no fix; migrate to a newer branch)

  1. 1. Identify the specific BIG-IP module(s) and version(s) running in your environment from the affected list (13.1.x, 14.1.0-14.1.5.0, 15.1.0-15.1.6, 16.1.0-16.1.3.0).
  2. 2. Determine the appropriate fixed version for your current major release branch.
  3. 3. Download the corresponding hotfix or update from the F5 Downloads portal at https://downloads.f5.com/ or obtain it through your F5 support account.
  4. 4. Review F5 release notes for the target version to understand any changes or prerequisites.
  5. 5. Schedule a maintenance window following your organization's change management procedures.
  6. 6. Back up the BIG-IP configuration before applying the update.
  7. 7. Apply the upgrade to the fixed version: 13.1.x -> 13.1.5.1+ (or migrate to a newer branch), 14.1.x -> 14.1.5.1+, 15.1.x -> 15.1.7+, or 16.1.x -> 16.1.3.1+.
  8. 8. Verify the upgrade was successful and that all services are functioning normally.
Caveat Upgrading between major versions may introduce configuration or compatibility changes; review F5 release notes and test in a non-production environment first

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
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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