dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2022-28691

HIGH · 7.5 CVSS v3.1 Published 2022-05-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
On F5 BIG-IP 16.1.x versions prior to 16.1.2.2, 15.1.x versions prior to 15.1.5, 14.1.x versions prior to 14.1.4.6, and 13.1.x versions prior to 13.1.5, when a Real Time Streaming Protocol (RTSP) profile is configured on a virtual server, undisclosed traffic can cause an increase in Traffic Management Microkernel (TMM) resource utilization. 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

A denial-of-service vulnerability in F5 BIG-IP where specially crafted Real Time Streaming Protocol (RTSP) traffic directed at a virtual server configured with an RTSP profile causes increased Traffic Management Microkernel (TMM) resource utilization, potentially leading to service degradation or availability loss.

MitigationUpgrade to F5 BIG-IP fixed versions (16.1.2.2, 15.1.5, 14.1.4.6, or 13.1.5) or disable/remove the RTSP profile from virtual servers if not 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.1= 13.1.3= 13.1.4= 13.1.5= 14.1.0= 14.1.2= 14.1.3= 14.1.4= 15.1.0= 15.1.1= 15.1.2
Big Ip Advanced Firewall ManagerApplication
Affected:= 13.1.0= 13.1.1= 13.1.3= 13.1.4= 13.1.5= 14.1.0= 14.1.2= 14.1.3= 14.1.4= 15.1.0= 15.1.1= 15.1.2
Big Ip AnalyticsApplication
Affected:= 13.1.0= 13.1.1= 13.1.3= 13.1.4= 13.1.5= 14.1.0= 14.1.2= 14.1.3= 14.1.4= 15.1.0= 15.1.1= 15.1.2
Big Ip Application Acceleration ManagerApplication
Affected:= 13.1.0= 13.1.1= 13.1.3= 13.1.4= 13.1.5= 14.1.0= 14.1.2= 14.1.3= 14.1.4= 15.1.0= 15.1.1= 15.1.2
Big Ip Application Security ManagerApplication
Affected:= 13.1.0= 13.1.1= 13.1.3= 13.1.4= 13.1.5= 14.1.0= 14.1.2= 14.1.3= 14.1.4= 15.1.0= 15.1.1= 15.1.2
Big Ip Domain Name SystemApplication
Affected:= 13.1.0= 13.1.1= 13.1.3= 13.1.4= 13.1.5= 14.1.0= 14.1.2= 14.1.3= 14.1.4= 15.1.0= 15.1.1= 15.1.2
Big Ip Fraud Protection ServiceApplication
Affected:= 13.1.0= 13.1.1= 13.1.3= 13.1.4= 13.1.5= 14.1.0= 14.1.2= 14.1.3= 14.1.4= 15.1.0= 15.1.1= 15.1.2
Big Ip Global Traffic ManagerApplication
Affected:= 13.1.0= 13.1.1= 13.1.3= 13.1.4= 13.1.5= 14.1.0= 14.1.2= 14.1.3= 14.1.4= 15.1.0= 15.1.1= 15.1.2

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 `bigpipe version` to retrieve the installed software version
    Affected if The version matches 13.1.0, 13.1.1, 13.1.3, 13.1.4, 13.1.5, 14.1.0, 14.1.2, 14.1.3, 14.1.4, 15.1.0, 15.1.1, or 15.1.2
  2. Verify RTSP profile exists
    Run `tmsh list /ltm profile rtsp` to list any RTSP profiles configured on the system
    Affected if Any RTSP profile is listed in the output
  3. Check virtual servers using RTSP profile
    Run `tmsh list /ltm virtual all` and search for lines containing 'rtsp' in the profiles section, or use `tmsh list /ltm virtual | grep -A 20 rtsp`
    Affected if Any virtual server references an RTSP profile in its configuration
  4. Monitor TMM resource utilization
    Run `tmsh show /ltm virtual-stat` or observe TMM CPU/memory metrics via the web UI under Dashboard > Performance
    Affected if Abnormally high TMM resource usage is observed, especially during RTSP traffic processing

You are affected if your BIG-IP version is one of the listed affected versions AND you have a virtual server configured with an RTSP profile receiving RTSP traffic.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to F5 BIG-IP fixed versions (16.1.2.2, 15.1.5, 14.1.4.6, or 13.1.5) or disable/remove the RTSP profile from virtual servers if not required.

Recommended fix High confidence

13.1.5 (or 14.1.4.6 / 15.1.5 / 16.1.2.2 depending on target branch)

  1. 1. Identify all virtual servers configured with an RTSP profile
  2. 2. Schedule a maintenance window for the upgrade
  3. 3. Before upgrading in production, test the upgrade in a staging or test environment
  4. 4. Upgrade F5 BIG-IP to version 13.1.5 or later for the 13.1.x branch
  5. 5. Alternatively, for longer support cycles, consider upgrading to 14.1.4.6+, 15.1.5+, or 16.1.2.2+ as appropriate for your deployment
  6. 6. After upgrade, verify virtual server functionality and monitor TMM resource utilization
  7. 7. Confirm the RTSP profile is functioning correctly with the new version
Caveat Standard upgrade considerations apply - review F5 release notes for known issues and ensure compatibility with existing configurations

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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