dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2022-41832

HIGH · 7.5 CVSS v3.1 Published 2022-10-19
Fix available
A fix is available. Upgrade to 13.1.5.1 / 14.1.5.1 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.6.1, 14.1.x before 14.1.5.1, and 13.1.x before 13.1.5.1, when a SIP profile is configured on a virtual server, undisclosed messages can cause an increase in memory resource utilization.

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

This is a denial-of-service vulnerability in F5 BIG-IP where specially crafted SIP (Session Initiation Protocol) messages sent to a virtual server configured with a SIP profile cause excessive memory consumption, potentially leading to resource exhaustion and service disruption.

MitigationUpgrade BIG-IP to the patched versions (17.0.0.1, 16.1.3.1, 15.1.6.1, 14.1.5.1, or 13.1.5.1). If immediate patching is not feasible, consider disabling the SIP profile on virtual servers where not required or implementing upstream traffic filtering to limit SIP messages.

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.1>= 14.1.0, < 14.1.5.1>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.3.1>= 17.0.0, < 17.0.0.1
Big Ip Advanced Firewall ManagerApplication
Affected:>= 13.1.0, < 13.1.5.1>= 14.1.0, < 14.1.5.1>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.3.1>= 17.0.0, < 17.0.0.1
Big Ip AnalyticsApplication
Affected:>= 13.1.0, < 13.1.5.1>= 14.1.0, < 14.1.5.1>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.3.1>= 17.0.0, < 17.0.0.1
Big Ip Application Acceleration ManagerApplication
Affected:>= 13.1.0, < 13.1.5.1>= 14.1.0, < 14.1.5.1>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.3.1>= 17.0.0, < 17.0.0.1
Big Ip Application Security ManagerApplication
Affected:>= 13.1.0, < 13.1.5.1>= 14.1.0, < 14.1.5.1>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.3.1>= 17.0.0, < 17.0.0.1
Big Ip Domain Name SystemApplication
Affected:>= 13.1.0, < 13.1.5.1>= 14.1.0, < 14.1.5.1>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.3.1>= 17.0.0, < 17.0.0.1
Big Ip Fraud Protection ServiceApplication
Affected:>= 13.1.0, < 13.1.5.1>= 14.1.0, < 14.1.5.1>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.3.1>= 17.0.0, < 17.0.0.1
Big Ip Global Traffic ManagerApplication
Affected:>= 13.1.0, < 13.1.5.1>= 14.1.0, < 14.1.5.1>= 15.1.0, < 15.1.6.1>= 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 'tmsh list /sys version' to obtain the installed version.
    Affected if The version falls within any of these ranges: 13.1.0 to 13.1.5.0, 14.1.0 to 14.1.5.0, 15.1.0 to 15.1.6.0, 16.1.0 to 16.1.3.0, or 17.0.0 only.
  2. Identify SIP profiles
    Run 'tmsh list /ltm profile sip' to list all SIP profiles configured on the system.
    Affected if Any SIP profile exists in the configuration.
  3. Check virtual servers using SIP profile
    Run 'tmsh list /ltm virtual all one-line' and examine the output for 'profile sip' or SIP profile references in the virtual server definitions.
    Affected if Any virtual server references a SIP profile in its configuration.
  4. Confirm vulnerability condition
    Cross-reference: if the BIG-IP version is in an affected range AND a virtual server has a SIP profile enabled, the system is vulnerable to the denial-of-service condition described in the CVE.
    Affected if Both conditions are true: (1) installed version is within affected ranges AND (2) at least one virtual server has a SIP profile configured.

You are affected if your BIG-IP version is within the vulnerable ranges AND you have a virtual server configured with a SIP profile that can receive specially crafted SIP messages.

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 13.1.5.1 / 14.1.5.1 / 15.1.6.1 or later
Fixed in 13.1.5.114.1.5.115.1.6.1
Interim mitigation

Upgrade BIG-IP to the patched versions (17.0.0.1, 16.1.3.1, 15.1.6.1, 14.1.5.1, or 13.1.5.1). If immediate patching is not feasible, consider disabling the SIP profile on virtual servers where not required or implementing upstream traffic filtering to limit SIP messages.

Recommended fix High confidence

13.1.5.1, 14.1.5.1, 15.1.6.1, 16.1.3.1, or 17.0.0.1 (depending on current branch)

  1. 1. Identify the current BIG-IP version by checking the system information in the web management interface or running 'tmsh show sys version'
  2. 2. Identify which BIG-IP modules (APM, AFM, Analytics, AAM, ASM, DNS, FPS, GTM) are in use and have SIP profiles configured on virtual servers
  3. 3. Review the F5 knowledge article K23605446 at support.f5.com for detailed upgrade procedures and any additional prerequisites
  4. 4. Schedule a maintenance window as upgrades require system restart
  5. 5. Create a UCS backup of the current configuration using 'tmsh save sys ucs <filename>'
  6. 6. For BIG-IP 13.1.x: upgrade to 13.1.5.1 or later
  7. 7. For BIG-IP 14.1.x: upgrade to 14.1.5.1 or later
  8. 8. For BIG-IP 15.1.x: upgrade to 15.1.6.1 or later
Caveat Review F5 release notes for your specific version upgrade path for any configuration or compatibility changes; test in non-production environment first

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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