dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2022-27636

MEDIUM · 5.5 CVSS v3.1 Published 2022-05-05
Fix available
A fix is available. Upgrade to after 7.2.1 or later.
See remediation →
57/100
Remediation priority · Elevated
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 F5 BIG-IP APM 16.1.x versions prior to 16.1.2.2, 15.1.x versions prior to 15.1.5.1, 14.1.x versions prior to 14.1.4.6, 13.1.x versions prior to 13.1.5, and all versions of 12.1.x and 11.6.x, as well as F5 BIG-IP APM Clients 7.x versions prior to 7.2.1.5, BIG-IP Edge Client may log sensitive APM session-related information when VPN is launched on a Windows system. 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

F5 BIG-IP Edge Client for Windows logs sensitive APM (Access Policy Manager) session-related information when VPN is launched. This exposes session tokens, credentials, or configuration data to local log files that could be accessed by local users or malware, leading to session hijacking or credential theft.

MitigationUpgrade F5 BIG-IP APM to version 16.1.2.2, 15.1.5.1, 14.1.4.6, or 13.1.5 or later, and upgrade BIG-IP Edge Client to 7.2.1.5 or later. Review log files on affected systems for any unauthorized access.

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:= 11.6.1= 11.6.2= 11.6.3= 11.6.4= 11.6.5= 12.1.0= 12.1.1= 12.1.2= 12.1.3= 12.1.4= 12.1.5= 12.1.6
Big Ip Access Policy Manager ClientApplication
Affected:>= 7.1.6, <= 7.2.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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 BIG-IP APM version
    Use the command 'tmsh show /sys version' or access the BIG-IP Configuration Utility to view the Access Policy Manager version
    Affected if The installed version matches 11.6.1, 11.6.2, 11.6.3, 11.6.4, 11.6.5, 12.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.4, 12.1.5, or 12.1.6
  2. Check BIG-IP Edge Client for Windows version
    Open Windows Programs and Features or use 'Get-ItemProperty' in PowerShell for the installed F5 BIG-IP Edge Client package
    Affected if The installed version is between 7.1.6 and 7.2.1 inclusive
  3. Verify APM client is in use
    Confirm the system has F5 BIG-IP Edge Client for Windows installed and is used to establish VPN connections via Access Policy Manager
    Affected if The Edge Client software is installed and used to connect to APM-protected resources

A system is affected if it runs BIG-IP APM versions 11.6.1-12.1.6 or BIG-IP Edge Client for Windows versions 7.1.6-7.2.1, and sensitive session data may be present in local log files accessible to other local 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 a release after 7.2.1
Interim mitigation

Upgrade F5 BIG-IP APM to version 16.1.2.2, 15.1.5.1, 14.1.4.6, or 13.1.5 or later, and upgrade BIG-IP Edge Client to 7.2.1.5 or later. Review log files on affected systems for any unauthorized access.

Recommended fix High confidence

BIG-IP APM 16.1.2.2+ (or 15.1.5.1+, 14.1.4.6+, 13.1.5+); BIG-IP APM Client 7.2.1.5+

  1. 1. Identify the exact BIG-IP APM version currently installed using 'tmsh show sys version' or through the web UI under System > Software Management.
  2. 2. For BIG-IP APM 16.1.x: Upgrade to version 16.1.2.2 or later.
  3. 3. For BIG-IP APM 15.1.x: Upgrade to version 15.1.5.1 or later.
  4. 4. For BIG-IP APM 14.1.x: Upgrade to version 14.1.4.6 or later.
  5. 5. For BIG-IP APM 13.1.x: Upgrade to version 13.1.5 or later.
  6. 6. For BIG-IP APM Client (Windows): Upgrade to version 7.2.1.5 or later.
  7. 7. After upgrade, verify the fix by testing VPN launch on Windows systems and confirming no sensitive session data appears in APM logs (/var/log/apm).
  8. 8. Note: Versions 12.1.x and 11.6.x are End of Technical Support (EoTS) and no patches will be released; migrate to a supported version.
Caveat Upgrading major versions may require compatibility review of existing policies and configurations; EoTS versions (11.6.x, 12.1.x) have no fix and require migration to supported releases

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
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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