dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2022-27806

HIGH · 7.2 CVSS v3.1 Published 2022-05-05
Fix available
A fix is available. Upgrade to 9.0 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
On all versions of 16.1.x, 15.1.x, 14.1.x, 13.1.x, 12.1.x, and 11.6.x of F5 BIG-IP Advanced WAF, ASM, and ASM, and F5 BIG-IP Guided Configuration (GC) all versions prior to 9.0, when running in Appliance mode, an authenticated attacker assigned the Administrator role may be able to bypass Appliance mode restrictions, utilizing command injection vulnerabilities in undisclosed URIs in F5 BIG-IP Guided Configuration. 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

Command injection vulnerabilities in undisclosed URIs of F5 BIG-IP Guided Configuration allow authenticated Administrator role users to bypass Appliance mode restrictions on BIG-IP Advanced WAF and ASM across versions 11.6.x through 16.1.x and Guided Configuration versions prior to 9.0. This enables privilege escalation beyond the intended appliance mode constraints.

MitigationUpgrade F5 BIG-IP Guided Configuration to version 9.0 or later, and upgrade BIG-IP Advanced WAF/ASM to a version beyond the listed affected versions that includes the security fix. Restrict Administrator role assignments until patching is complete.

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.1= 13.1.3= 13.1.4= 13.1.5= 14.1.0= 14.1.2= 14.1.3= 14.1.4= 15.1.0= 15.1.1= 15.1.2
Big Ip Advanced Web Application FirewallApplication
Affected:= 13.1.0= 13.1.1= 13.1.3= 13.1.4= 13.1.5= 14.1.0= 14.1.2= 14.1.3= 14.1.4= 15.1.0= 15.1.1= 15.1.2
Big Ip Application Security ManagerApplication
Affected:= 13.1.0= 13.1.1= 13.1.3= 13.1.4= 13.1.5= 14.1.0= 14.1.2= 14.1.3= 14.1.4= 15.1.0= 15.1.1= 15.1.2
Big Ip Guided ConfigurationApplication
Affected:< 9.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
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. Check Guided Configuration version
    Run command: tmsh list sys software volume one-line | grep -i guided or check via GUI: System > Software > Guided Configuration > Version
    Affected if Version is prior to 9.0 (e.g., 8.x, 7.x, etc.)
  2. Check BIG-IP system version
    Run command: tmsh show sys version or check via GUI: Dashboard > Overview > System > Version
    Affected if Running version 11.6.x through 16.1.x with Guided Configuration < 9.0 installed
  3. Verify Guided Configuration module status
    Run command: tmsh list sys module httpd or check GUI: iControl > System > Software > Guided Configuration - confirm the service is provisioned and accessible
    Affected if Guided Configuration module is provisioned and accessible to the Administrator
  4. Check if Appliance mode is enabled
    Run command: tmsh list sys db ui.appliance mode or tmsh show sys auth user admin for appliance-mode restrictions
    Affected if Appliance mode restrictions are configured on the system
  5. Confirm Administrator role access exists
    Review user accounts: tmsh list auth user or check GUI: User Management > User List
    Affected if Any user with Administrator role has access to Guided Configuration interfaces

System is affected if running BIG-IP Advanced WAF or ASM versions 11.6.x through 16.1.x with Guided Configuration version prior to 9.0 and the Guided Configuration module is accessible to Administrator role users, particularly when Appliance mode is in use.

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 9.0 or later
Fixed in 9.0
Interim mitigation

Upgrade F5 BIG-IP Guided Configuration to version 9.0 or later, and upgrade BIG-IP Advanced WAF/ASM to a version beyond the listed affected versions that includes the security fix. Restrict Administrator role assignments until patching is complete.

Recommended fix Moderate confidence

F5 BIG-IP Guided Configuration: upgrade to 9.0 or later; For APM/ASM/AWAF 13.1.x: upgrade to a fixed version as specified in F5 K34534667

  1. 1. Identify the current version of F5 BIG-IP Guided Configuration by navigating to the Guided Configuration interface or checking the system information.
  2. 2. If Guided Configuration version is below 9.0, upgrade to version 9.0 or later from F5's download portal at support.f5.com.
  3. 3. For BIG-IP APM, ASM, and AWAF versions 13.1.0-13.1.4, upgrade to a version that includes the security fix. Consult F5 K34534667: https://support.f5.com/csp/article/K34534667 for the complete list of affected versions and fixed releases.
  4. 4. After upgrading, verify the Appliance mode restrictions are functioning correctly.
  5. 5. Review Administrator role assignments and ensure only necessary users have Administrator privileges.
  6. 6. Monitor F5 security advisories for any further updates.
Caveat Upgrading BIG-IP software may require downtime and could affect existing configurations - 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
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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