dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2022-34851

MEDIUM · 6.5 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 →
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.6.1, 14.1.x before 14.1.5.1, and all versions of 13.1.x, and BIG-IQ Centralized Management all versions of 8.x, an authenticated attacker may cause iControl SOAP to become unavailable through undisclosed requests. 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

An authenticated attacker can cause iControl SOAP to become unavailable through undisclosed requests, resulting in a denial of service condition. This affects multiple BIG-IP versions (13.1.x, 14.1.x, 15.1.x, 16.1.x, 17.0.x) and BIG-IQ Centralized Management 8.x.

MitigationUpgrade BIG-IP to version 17.0.0.1, 16.1.3.1, 15.1.6.1, or 14.1.5.1 respectively, and upgrade BIG-IQ CM to a patched version once available. Until patched, monitor for unusual authenticated requests to 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 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
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 installed BIG-IP version
    Run `tmsh show sys version` on the BIG-IP command line, or check System > Information > Software Version in the web UI
    Affected if The version shown falls 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 equals exactly 17.0.0
  2. Identify installed BIG-IQ CM version if applicable
    Run `tmsh show sys version` on the BIG-IQ Centralized Management system, or check System > Information in the web UI
    Affected if The BIG-IQ CM version is 8.x and falls within the affected range for that platform
  3. Verify iControl SOAP service is accessible
    Check if the iControl SOAP service is running by reviewing virtual server configurations via `tmsh show /ltm virtual` or by confirming the iControl SOAP port (443 or 8443) is open and listening
    Affected if iControl SOAP endpoints are exposed and reachable on the system
  4. Confirm the attack surface exists
    Review system logs or access profiles to determine if authenticated users can make requests to iControl SOAP endpoints
    Affected if Authenticated users have access to iControl SOAP functionality, which is the attack vector for this DoS condition

You are affected if your BIG-IP 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, 16.1.0 through 16.1.3.0, or exactly 17.0.0, and iControl SOAP is enabled and accessible to authenticated users.

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 respectively, and upgrade BIG-IQ CM to a patched version once available. Until patched, monitor for unusual authenticated requests to iControl SOAP endpoints.

Recommended fix High confidence

Upgrade to BIG‑IP 14.1.5.1 / 15.1.6.1 / 16.1.3.1 / 17.0.0.1 (or later, depending on your branch)

  1. Identify the currently installed BIG‑IP version (e.g., run 'tmsh show sys version').
  2. If the version is 13.1.x, plan to migrate to a supported branch (14.1.x, 15.1.x, 16.1.x, or 17.0.x) because 13.1.x has no fix.
  3. Select a target release that includes the security fix: 14.1.5.1 or later, 15.1.6.1 or later, 16.1.3.1 or later, or 17.0.0.1 or later.
  4. Review the F5 BIG‑IP upgrade guide and ensure the target version is supported for your hardware platform.
  5. Back up the BIG‑IP configuration (e.g., using 'tmsh save sys config' and generate a UCS archive).
  6. If possible, test the upgrade in a non‑production environment to confirm iControl SOAP remains available.
  7. Apply the upgrade (either in‑place or via hot‑swap) following F5's recommended procedures.
  8. After reboot, verify that iControl SOAP is operational (e.g., via 'tmsh show icontrol soap' or a test SOAP request).
Caveat Upgrading across major branches may require configuration adjustments; review release notes for any breaking changes.

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
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
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,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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