Big Iq Centralized ManagementApplication · F5

CVE-2022-41622

HIGH · 8.8 CVSS v3.1 Published 2022-12-07
Fix available
A fix is available. Upgrade to after 16.1.3 or later.
See remediation →
95/100
Remediation priority · Urgent
High EPSS Remotely reachable No privileges

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 all versions,  BIG-IP and BIG-IQ are vulnerable to cross-site request forgery (CSRF) attacks through iControl SOAP.   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

A cross-site request forgery (CSRF) vulnerability exists in iControl SOAP across all versions of BIG-IP and BIG-IQ. Attackers can exploit this to trick authenticated administrators into unknowingly executing unauthorized configuration changes or administrative actions through forged SOAP requests.

MitigationApply the F5-provided security update for BIG-IP and BIG-IQ to implement proper anti-CSRF token validation in iControl SOAP endpoints.

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 Iq Centralized ManagementApplication
Affected:>= 8.0.0, <= 8.2.0= 7.1.0
Big Ip Advanced Firewall ManagerApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, <= 14.1.5>= 15.1.0, <= 15.1.8>= 16.1.0, <= 16.1.3= 17.0.0
Big Ip AnalyticsApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, <= 14.1.5>= 15.1.0, <= 15.1.8>= 16.1.0, <= 16.1.3= 17.0.0
Big Ip Access Policy ManagerApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, <= 14.1.5>= 15.1.0, <= 15.1.8>= 16.1.0, <= 16.1.3= 17.0.0
Big Ip Application Security ManagerApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, <= 14.1.5>= 15.1.0, <= 15.1.8>= 16.1.0, <= 16.1.3= 17.0.0
Big Ip Domain Name SystemApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, <= 14.1.5>= 15.1.0, <= 15.1.8>= 16.1.0, <= 16.1.3= 17.0.0
Big Ip Fraud Protection ServiceApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, <= 14.1.5>= 15.1.0, <= 15.1.8>= 16.1.0, <= 16.1.3= 17.0.0
Big Ip Global Traffic ManagerApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, <= 14.1.5>= 15.1.0, <= 15.1.8>= 16.1.0, <= 16.1.3= 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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 product and version
    Run 'show version' in tmsh (tmsh show version) or use 'tmctl -c version' to get the installed BIG-IP or BIG-IQ version
    Affected if The version falls within 13.1.0-13.1.5, 14.1.0-14.1.5, 15.1.0-15.1.8, 16.1.0-16.1.3, 17.0.0 for BIG-IP or 7.1.0, 8.0.0-8.2.0 for BIG-IQ
  2. Confirm iControl SOAP is enabled
    Check the iControl SOAP service status via tmsh: 'show sys service icrsoap' or review the iControl SOAP configuration in the GUI under iControl > SOAP
    Affected if iControl SOAP service is running and accessible on the device
  3. Check iControl SOAP endpoint exposure
    Verify iControl SOAP endpoints are exposed externally by reviewing the BIG-IP IP addressing configuration or using 'list sys httpd' to see which interfaces have iControl enabled
    Affected if iControl SOAP is bound to management or other accessible interfaces without network restrictions
  4. Verify anti-CSRF protection status
    Review the iControl SOAP configuration for any configured anti-CSRF tokens or review system logs for recent configuration changes initiated via iControl SOAP that may be unauthorized
    Affected if No anti-CSRF token validation is configured for iControl SOAP requests

You are affected if your BIG-IP or BIG-IQ version is within the listed ranges and iControl SOAP is enabled without proper anti-CSRF token validation in place.

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 a release after 16.1.3
Interim mitigation

Apply the F5-provided security update for BIG-IP and BIG-IQ to implement proper anti-CSRF token validation in iControl SOAP endpoints.

Recommended fix Moderate confidence

BIG-IP: 13.1.6+ or 14.1.6+ or 15.1.9+ or 16.1.4+ (or latest stable 17.x); BIG-IQ: 8.2.1+ (or latest stable 8.x)

  1. Verify your current BIG-IP or BIG-IQ version by running 'tmsh show sys version' or checking the web UI.
  2. Identify which specific product(s) in your environment are affected (Big IP AFM, APM, ASM, DNS, GTM, Analytics, FPS, or Big IQ Centralized Management).
  3. Contact F5 Networks technical support or visit support.f5.com to obtain the specific hotfix or fixed version for your product line.
  4. Apply the hotfix or upgrade to a fixed version as provided by F5. For BIG-IP, versions 13.1.6+, 14.1.6+, 15.1.9+, and 16.1.4+ contain the fixes. For BIG-IQ, version 8.2.1+ contains the fix.
  5. After applying the fix, verify the version has been updated and confirm the iControl SOAP endpoint now properly validates CSRF tokens.
  6. Test that legitimate iControl SOAP operations continue to function correctly after the update.
Caveat Review F5 release notes for your target version to check for configuration or API compatibility changes before upgrading.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Big Iq Centralized Management Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-41622 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-41622 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