dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2022-28714

HIGH · 7.8 CVSS v3.1 Published 2022-05-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
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
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, a DLL Hijacking vulnerability exists in the BIG-IP Edge Client Windows Installer. 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

A DLL Hijacking vulnerability exists in the BIG-IP Edge Client Windows Installer. This allows the installer to load malicious DLL files from attacker-controlled locations, potentially executing arbitrary code with the privileges of the user running the installer.

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 APM Clients to version 7.2.1.5 or later.

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.5= 7.1.6= 7.1.6.1= 7.1.7= 7.1.8= 7.1.8.2= 7.1.9= 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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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 installed F5 BIG-IP APM version
    Open Windows Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product' or check registry at HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall for F5 BIG-IP APM entry. Locate the 'DisplayVersion' field.
    Affected if The version displayed 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. Identify installed F5 BIG-IP APM Client version
    Open Windows Control Panel > Programs and Features, or check registry at HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall for F5 Big-IP APM Client entry. Locate the 'DisplayVersion' field.
    Affected if The version displayed matches 7.1.5, 7.1.6, 7.1.6.1, 7.1.7, 7.1.8, 7.1.8.2, 7.1.9, or 7.1.10, or 7.2.1.
  3. Confirm Windows installer is being used
    Verify the F5 software was installed using the Windows installer (.msi or setup.exe) rather than a different deployment method.
    Affected if The software was installed via Windows installer on a Windows system.

You are affected if either the BIG-IP APM or BIG-IP APM Client version matches one of the listed vulnerable versions and the software was installed using the Windows installer.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
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 APM Clients to version 7.2.1.5 or later.

Recommended fix High confidence

BIG-IP APM: 16.1.2.2+ / 15.1.5.1+ / 14.1.4.6+ / 13.1.5+; BIG-IP APM Client: 7.2.1.5+ (Note: 11.6.x and 12.1.x are EoTS and not patched)

  1. 1. Identify the currently installed BIG-IP APM version using the web management console or tmsh command line (run 'show /sys version' or check System > Software Management > BIG-IP Version)
  2. 2. For BIG-IP APM: upgrade to the minimum fixed version for your major release line: 16.1.2.2 or later, 15.1.5.1 or later, 14.1.4.6 or later, or 13.1.5 or later
  3. 3. For BIG-IP APM Client (Windows): upgrade to version 7.2.1.5 or later
  4. 4. After upgrade, verify the new version is installed by checking System > Software Management > BIG-IP Version
  5. 5. For BIG-IP APM Client, verify the updated client is pushed to endpoints via the APM client configuration profile
Caveat Review F5 release notes for your version path for potential compatibility changes; note that 11.6.x and 12.1.x versions have reached End of Technical Support and do not receive patches

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
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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