dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2022-34865

CRITICAL · 9.1 CVSS v3.1 Published 2022-08-04
Fix available
A fix is available. Upgrade to 14.1.5 / 15.1.6.1 or later.
See remediation →
100/100
Remediation priority · Urgent
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 BIG-IP Versions 15.1.x before 15.1.6.1, 14.1.x before 14.1.5, and all versions of 13.1.x, Traffic Intelligence feeds, which use HTTPS, do not verify the remote endpoint identity, allowing for potential data poisoning. 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

Traffic Intelligence feeds in BIG-IP use HTTPS but fail to verify the remote endpoint's TLS certificate identity, allowing man-in-the-middle attackers to impersonate the remote server and poison the data being ingested by the feeds.

MitigationUpgrade BIG-IP to version 15.1.6.1 or later, or 14.1.5 or later. For 13.1.x versions (EoTS), migration to a supported version is required.

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.5>= 14.1.0, < 14.1.5>= 15.1.0, < 15.1.6.1
Big Ip Advanced Firewall ManagerApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5>= 15.1.0, < 15.1.6.1
Big Ip AnalyticsApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5>= 15.1.0, < 15.1.6.1
Big Ip Application Acceleration ManagerApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5>= 15.1.0, < 15.1.6.1
Big Ip Application Security ManagerApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5>= 15.1.0, < 15.1.6.1
Big Ip Domain Name SystemApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5>= 15.1.0, < 15.1.6.1
Big Ip Fraud Protection ServiceApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5>= 15.1.0, < 15.1.6.1
Big Ip Global Traffic ManagerApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5>= 15.1.0, < 15.1.6.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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 version
    Run `tmsh show sys version` on the command line, or check System > Overview in the BIG-IP Configuration Utility web interface
    Affected if The version falls within 13.1.0-13.1.5, 14.1.0-14.1.4, or 15.1.0-15.1.6.0
  2. Locate Traffic Intelligence feed configurations
    Review BIG-IP LTM or GTM configuration for external feed definitions. Use `tmsh list ltm external-data` or check for iRules referencing external feed URLs
    Affected if Any Traffic Intelligence or external data feed sources are configured to pull data from remote HTTPS endpoints
  3. Verify feed source connectivity
    Examine the defined feed URLs in the configuration. Confirm they use HTTPS protocol
    Affected if Feed sources are configured with HTTPS URLs pointing to remote endpoints

The environment is affected if BIG-IP version is 13.1.0-13.1.5, 14.1.0-14.1.4, or 15.1.0-15.1.6.0 AND Traffic Intelligence feeds pulling data from external HTTPS endpoints are configured.

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 14.1.5 / 15.1.6.1 or later
Fixed in 14.1.515.1.6.1
Interim mitigation

Upgrade BIG-IP to version 15.1.6.1 or later, or 14.1.5 or later. For 13.1.x versions (EoTS), migration to a supported version is required.

Recommended fix High confidence

15.1.6.1 (for 15.1.x), 14.1.5 (for 14.1.x), or migrate off 13.1.x to 14.1.5+/15.1.6.1+ (13.1.x is EoTS)

  1. Identify the exact BIG-IP version currently installed using 'tmsh show sys version'
  2. For BIG-IP 15.1.x versions: Upgrade to version 15.1.6.1 or later
  3. For BIG-IP 14.1.x versions: Upgrade to version 14.1.5 or later
  4. For BIG-IP 13.1.x versions: These have reached End of Technical Support (EoTS) and no patch is available; migrate to a supported version (14.1.5+ or 15.1.6.1+)
  5. After upgrade, verify the fix by confirming that HTTPS Traffic Intelligence feeds now properly validate certificates
Caveat Upgrading BIG-IP major versions may require careful planning; review F5 upgrade guides for configuration compatibility and test in staging 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 / QA4.0 h
22.0 hours of engineering $3,860
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,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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