dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2022-23032

MEDIUM · 5.3 CVSS v3.1 Published 2022-01-25
Fix available
A fix is available. Upgrade to after 16.1.2 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 all versions before 7.2.1.4, when proxy settings are configured in the network access resource of a BIG-IP APM system, connecting BIG-IP Edge Client on Mac and Windows is vulnerable to a DNS rebinding attack. 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

In BIG-IP APM versions before 7.2.1.4, when proxy settings are configured in the network access resource, the BIG-IP Edge Client on Mac and Windows is vulnerable to DNS rebinding attacks. This allows an attacker to potentially bypass security controls by manipulating DNS responses to control the apparent origin of requests.

MitigationUpgrade BIG-IP APM to version 7.2.1.4 or later. Until the upgrade can be performed, consider disabling or restricting proxy configurations in network access resources and implementing additional network-level DNS validation controls.

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.5>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.5>= 16.0.0, <= 16.1.2
Big Ip Access Policy Manager ClientApplication
Affected:>= 7.1.6, <= 7.1.9>= 7.2.1, <= 7.2.1.3

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Identify BIG-IP APM version
    Run 'tmsh show sys version' or check the GUI under System > Software Management > BIG-IP Version to determine the installed BIG-IP APM version
    Affected if Version falls within 11.6.1-11.6.5, 12.1.0-12.1.6, 13.1.0-13.1.4, 14.1.0-14.1.4, 15.1.0-15.1.5, or 16.0.0-16.1.2
  2. Identify BIG-IP APM Client version
    Check the installed Edge Client version on Mac or Windows systems using the client application or its installer information
    Affected if Client version falls within 7.1.6-7.1.9 or 7.2.1-7.2.1.3
  3. Locate network access resources with proxy configuration
    Access BIG-IP APM configuration via tmsh or management GUI and search for network access profiles that have proxy settings enabled. Use 'tmsh list apm profile network-access' to list network access profiles and inspect for proxy-server and proxy-port settings
    Affected if Proxy settings (proxy-server or proxy-port) are explicitly configured in any network access resource

Environment is affected if both the BIG-IP APM or its client version is within the affected ranges AND proxy settings are configured in network access resources.

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 16.1.2
Interim mitigation

Upgrade BIG-IP APM to version 7.2.1.4 or later. Until the upgrade can be performed, consider disabling or restricting proxy configurations in network access resources and implementing additional network-level DNS validation controls.

Recommended fix High confidence

BIG-IP Edge Client upgrade to 7.2.1.4 or later; BIG-IP APM should be upgraded to a currently supported version (15.x or later)

  1. 1. Identify the currently installed BIG-IP Edge Client version on Mac and Windows systems.
  2. 2. Upgrade BIG-IP Edge Client for Mac and Windows from any version >= 7.1.6 and <= 7.1.9, or >= 7.2.1 and <= 7.2.1.3, to version 7.2.1.4 or later.
  3. 3. Verify that proxy settings are configured in the network access resource of the BIG-IP APM system.
  4. 4. After upgrading the client, test the connection to ensure the DNS rebinding vulnerability is mitigated.
  5. 5. Ensure the BIG-IP APM itself is also updated to a version that includes the fix; F5 recommends moving to a currently supported release branch.
Caveat Upgrading major versions of BIG-IP may require configuration review and testing; ensure compatibility with existing network access policies before upgrading

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
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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