Big Ip Access Policy ManagerApplication · F5

CVE-2023-22358

HIGH · 7.8 CVSS v3.1 Published 2023-02-01
Fix available
A fix is available. Upgrade to 7.2.3.1 / 17.0.0.2 or later.
See remediation →
80/100
Remediation priority · High
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 versions beginning with 7.2.2 to before 7.2.3.1, 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 · moderate confidence

A DLL hijacking vulnerability exists in the BIG-IP Edge Client Windows Installer for versions 7.2.2 through 7.2.3.0, allowing an attacker to execute arbitrary code by placing a malicious DLL in a location where the installer will load it, likely during the installation process.

MitigationUpdate BIG-IP Edge Client to version 7.2.3.1 or later to remediate the vulnerability. Review and verify no vulnerable versions remain deployed in the environment.

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:>= 7.2.2, < 7.2.3.1>= 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, < 17.0.0.2
Big Ip EdgeWeb browser
Affected:all versions

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
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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. Identify installed BIG-IP Edge Client version
    On the Windows system, check the installed version of BIG-IP Edge Client. This can typically be found in Add/Remove Programs, or by checking the application's version information if already installed.
    Affected if The installed version falls between 7.2.2 and 7.2.3.0 inclusive.
  2. Check Access Policy Manager version
    Verify the version of F5 Big Ip Access Policy Manager (APM) installed in the environment. Compare against the affected version ranges: 7.2.2 to <7.2.3.1, 13.1.0 to 13.1.5, 14.1.0 to 14.1.5, 15.1.0 to 15.1.8, 16.1.0 to 16.1.3, or 17.0.0 to <17.0.0.2.
    Affected if The APM version matches any of the listed affected ranges.
  3. Confirm Windows installer is in use
    Determine whether the Windows version of the BIG-IP Edge Client installer is being used, since this DLL hijacking vulnerability affects only the Windows installer package.
    Affected if The Windows installer for BIG-IP Edge Client version 7.2.2 to 7.2.3.0 is present or was recently used.
  4. Check for F5 Big Ip Edge installation
    Identify if F5 Big Ip Edge client is installed, as the vulnerability listing indicates all versions of this product are affected.
    Affected if F5 Big Ip Edge client of any version is installed on the system.

You are affected if BIG-IP Edge Client Windows Installer version 7.2.2 through 7.2.3.0 was used, or if any version of F5 Big Ip Edge client is installed, or if Access Policy Manager matches the vulnerable version ranges.

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 7.2.3.1 / 17.0.0.2 or later
Fixed in 7.2.3.117.0.0.2
Interim mitigation

Update BIG-IP Edge Client to version 7.2.3.1 or later to remediate the vulnerability. Review and verify no vulnerable versions remain deployed in the environment.

Recommended fix High confidence

7.2.3.1 or later

  1. Upgrade BIG-IP Edge Client Windows Installer to version 7.2.3.1 or later

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
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,420
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,872.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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