dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2022-36795

HIGH · 7.5 CVSS v3.1 Published 2022-10-19
Fix available
A fix is available. Upgrade to 14.1.5.1 / 15.1.7 or later.
See remediation →
84/100
Remediation priority · High
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 17.0.x before 17.0.0.1, 16.1.x before 16.1.3.1, 15.1.x before 15.1.7, and 14.1.x before 14.1.5.1, when an LTM TCP profile with Auto Receive Window Enabled is configured on a virtual server, undisclosed traffic can cause the virtual server to stop processing new client connections.

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 denial-of-service vulnerability exists in F5 BIG-IP where an LTM TCP profile with Auto Receive Window Enabled enabled on a virtual server can be crashed by specific undisclosed traffic patterns, causing the virtual server to stop accepting new client connections.

MitigationApply the vendor-supplied patches: upgrade to 17.0.0.1+, 16.1.3.1+, 15.1.7+, or 14.1.5.1+ depending on the deployed version line. Alternatively, identify and modify TCP profiles with Auto Receive Window Enabled to disable that feature until patching is possible.

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:>= 14.1.0, < 14.1.5.1>= 15.1.0, < 15.1.7>= 16.1.0, < 16.1.3.1>= 17.0.0, < 17.0.0.1
Big Ip Advanced Firewall ManagerApplication
Affected:>= 14.1.0, < 14.1.5.1>= 15.1.0, < 15.1.7>= 16.1.0, < 16.1.3.1>= 17.0.0, < 17.0.0.1
Big Ip AnalyticsApplication
Affected:>= 14.1.0, < 14.1.5.1>= 15.1.0, < 15.1.7>= 16.1.0, < 16.1.3.1>= 17.0.0, < 17.0.0.1
Big Ip Application Acceleration ManagerApplication
Affected:>= 14.1.0, < 14.1.5.1>= 15.1.0, < 15.1.7>= 16.1.0, < 16.1.3.1>= 17.0.0, < 17.0.0.1
Big Ip Application Security ManagerApplication
Affected:>= 14.1.0, < 14.1.5.1>= 15.1.0, < 15.1.7>= 16.1.0, < 16.1.3.1>= 17.0.0, <= 17.0.0.1
Big Ip Domain Name SystemApplication
Affected:>= 14.1.0, < 14.1.5.1>= 15.1.0, < 15.1.7>= 16.1.0, < 16.1.3.1>= 17.0.0, < 17.0.0.1
Big Ip Fraud Protection ServiceApplication
Affected:>= 14.1.0, < 14.1.5.1>= 15.1.0, < 15.1.7>= 16.1.0, < 16.1.3.1>= 17.0.0, < 17.0.0.1
Big Ip Global Traffic ManagerApplication
Affected:>= 14.1.0, < 14.1.5.1>= 15.1.0, < 15.1.7>= 16.1.0, < 16.1.3.1>= 17.0.0, < 17.0.0.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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Check BIG-IP version
    Run 'tmsh show sys version' or view System > Software Management > Installation List in the GUI to identify the installed version
    Affected if Version falls within 14.1.0 to 14.1.5.0, 15.1.0 to 15.1.6, 16.1.0 to 16.1.3.0, or 17.1.0 to 17.1.0.0 (any version before the fixed releases)
  2. Identify TCP profiles with Auto Receive Window Enabled
    Run 'tmsh list ltm profile tcp all properties include autoReceiveWindow' or navigate to Local Traffic > Profiles > TCP in the GUI and inspect each profile for the Auto Receive Window Enabled setting
    Affected if Any LTM TCP profile has Auto Receive Window Enabled set to Enabled (checked)
  3. Check which virtual servers use affected TCP profiles
    Run 'tmsh list ltm virtual all' and examine the 'profiles' section of each virtual server to see if it references a TCP profile with Auto Receive Window Enabled, or use the GUI at Local Traffic > Virtual Servers to view profile associations
    Affected if A virtual server is using a TCP profile where Auto Receive Window Enabled is turned on

You are affected if your BIG-IP version is less than the fixed releases (14.1.5.1+, 15.1.7+, 16.1.3.1+, 17.0.0.1+) AND you have any virtual server using a TCP profile with Auto Receive Window Enabled 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 14.1.5.1 / 15.1.7 / 16.1.3.1 or later
Fixed in 14.1.5.115.1.716.1.3.1
Interim mitigation

Apply the vendor-supplied patches: upgrade to 17.0.0.1+, 16.1.3.1+, 15.1.7+, or 14.1.5.1+ depending on the deployed version line. Alternatively, identify and modify TCP profiles with Auto Receive Window Enabled to disable that feature until patching is possible.

Recommended fix High confidence

14.1.5.1, 15.1.7, 16.1.3.1, or 17.0.0.1 (or later stable releases within each respective major version branch)

  1. 1. Identify the current BIG-IP version by checking the system information in the web management console or via command line (tmsh show sys version).
  2. 2. Identify which BIG-IP modules (LTM, APM, AFM, Analytics, AAM, ASM, DNS, FPS, GTM) are in use and their versions.
  3. 3. Verify that any virtual servers are configured with an LTM TCP profile that has Auto Receive Window Enabled.
  4. 4. Plan maintenance window for upgrade as this may require brief service interruption.
  5. 5. Download the appropriate fixed version from F5 Networks support portal: 14.1.5.1 for 14.1.x, 15.1.7 for 15.1.x, 16.1.3.1 for 16.1.x, or 17.0.0.1 for 17.0.x.
  6. 6. Follow F5 upgrade documentation to apply the update, ensuring proper backup of configuration before proceeding.
  7. 7. After upgrade, verify that virtual servers with Auto Receive Window Enabled TCP profiles are processing connections normally.

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
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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