dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2022-35272

MEDIUM · 5.5 CVSS v3.1 Published 2022-08-04
Fix available
A fix is available. Upgrade to 16.1.3.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
In BIG-IP Versions 17.0.x before 17.0.0.1 and 16.1.x before 16.1.3.1, when source-port preserve-strict is configured on an HTTP Message Routing Framework (MRF) virtual server, undisclosed traffic may cause the Traffic Management Microkernel (TMM) to produce a core file and the connection to terminate. 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

In F5 BIG-IP versions 17.0.x before 17.0.0.1 and 16.1.x before 16.1.3.1, when source-port preserve-strict is configured on an HTTP Message Routing Framework (MRF) virtual server, certain undisclosed traffic patterns can trigger the Traffic Management Microkernel (TMM) to generate a core file and terminate the connection, resulting in a denial-of-service condition.

MitigationUpgrade BIG-IP to version 17.0.0.1 or later, or 16.1.3.1 or later. Alternatively, until patching is possible, avoid using source-port preserve-strict configuration on HTTP MRF virtual servers.

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:>= 16.1.0, < 16.1.3.1= 17.0.0
Big Ip Advanced Firewall ManagerApplication
Affected:>= 16.1.0, < 16.1.3.1= 17.0.0
Big Ip AnalyticsApplication
Affected:>= 16.1.0, < 16.1.3.1= 17.0.0
Big Ip Application Acceleration ManagerApplication
Affected:>= 16.1.0, < 16.1.3.1= 17.0.0
Big Ip Application Security ManagerApplication
Affected:>= 16.1.0, < 16.1.3.1= 17.0.0
Big Ip Domain Name SystemApplication
Affected:>= 16.1.0, < 16.1.3.1= 17.0.0
Big Ip Fraud Protection ServiceApplication
Affected:>= 16.1.0, < 16.1.3.1= 17.0.0
Big Ip Global Traffic ManagerApplication
Affected:>= 16.1.0, < 16.1.3.1= 17.0.0

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 the BIG-IP version
    Run 'tmsh show sys version' or check the GUI System > Overview page to determine the installed BIG-IP version
    Affected if Version is 16.1.0 through 16.1.3.0, or exactly 17.0.0 (versions before 16.1.0 are not affected, and versions 16.1.3.1 or later / 17.0.0.1 or later are patched)
  2. Confirm the product module
    Verify the BIG-IP module in use is one of the affected products: Access Policy Manager, Advanced Firewall Manager, Analytics, Application Acceleration Manager, Application Security Manager, Domain Name System, Fraud Protection Service, or Global Traffic Manager
    Affected if Any of these modules are running on an affected BIG-IP version
  3. Locate HTTP MRF virtual servers
    List virtual servers configured with HTTP profile type by running 'tmsh list ltm virtual one-line' and reviewing output for MRF (Message Routing Framework) related configurations
    Affected if Any virtual servers are configured using HTTP MRF (Message Routing Framework)
  4. Check for source-port preserve-strict configuration
    For each HTTP MRF virtual server, run 'tmsh list ltm virtual <virtual_name>' and examine the source-port setting; look specifically for 'source-port preserve-strict' in the configuration
    Affected if The virtual server has 'source-port preserve-strict' explicitly configured in the source-port settings

You are affected if your BIG-IP version is 16.1.0-16.1.3.0 or exactly 17.0.0, and you have an HTTP MRF virtual server configured with source-port preserve-strict enabled.

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 16.1.3.1 or later
Fixed in 16.1.3.1
Interim mitigation

Upgrade BIG-IP to version 17.0.0.1 or later, or 16.1.3.1 or later. Alternatively, until patching is possible, avoid using source-port preserve-strict configuration on HTTP MRF virtual servers.

Recommended fix High confidence

BIG-IP 16.1.3.1 or later (16.1.x branch); BIG-IP 17.0.0.1 or later (17.0.x branch)

  1. 1. Identify all BIG-IP devices running affected versions (16.1.0 - 16.1.3.0 or 17.0.0)
  2. 2. Identify virtual servers with HTTP Message Routing Framework (MRF) that have 'source-port preserve-strict' configured
  3. 3. Back up the current BIG-IP configuration
  4. 4. Schedule a maintenance window for the upgrade
  5. 5. Upgrade BIG-IP 16.1.x systems to version 16.1.3.1 or later
  6. 6. Upgrade BIG-IP 17.0.0 systems to version 17.0.0.1 or later
  7. 7. After upgrade, verify virtual server configuration and test connectivity
  8. 8. Monitor TMM logs and core files to confirm the vulnerability is resolved
Caveat Review release notes for any known issues between current and target versions 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
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,960
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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