dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2022-26130

MEDIUM · 5.3 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 →
62/100
Remediation priority · Elevated
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.1, 14.1.x versions prior to 14.1.4.6, and 13.1.x versions prior to 13.1.5, when an Active mode-enabled FTP profile is configured on a virtual server, undisclosed traffic can cause the virtual server to stop processing active FTP data channel connections. 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

F5 BIG-IP vulnerability where Active mode-enabled FTP profiles on virtual servers can be disrupted by specific traffic, causing the virtual server to stop processing FTP data channel connections. This is a denial-of-service condition triggered by undisclosed traffic patterns.

MitigationUpgrade F5 BIG-IP to patched versions (16.1.2.2, 15.1.5.1, 14.1.4.6, or 13.1.5) or temporarily disable Active mode FTP profiles on affected virtual servers if upgrading is not immediately feasible.

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
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

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 log into the Configuration Utility and check the BIG-IP version under System > Software Management > Volume
    Affected if The installed version matches 13.1.0-13.1.5, 14.1.0-14.1.4, or 15.1.0-15.1.2 from the affected version list
  2. Identify FTP profiles configured on the system
    Run 'tmsh list ltm ftp-profile all' or navigate to Local Traffic > Profiles > FTP in the Configuration Utility to list all FTP profiles
    Affected if Any FTP profile exists on the system
  3. Verify Active mode is enabled on FTP profiles
    Run 'tmsh list ltm ftp-profile <profile_name> all' for each FTP profile and check the 'allow-active-mode' setting, or inspect the profile in the Configuration Utility under the FTP profile settings
    Affected if An FTP profile has 'allow-active-mode' set to 'enabled' or 'yes'
  4. Identify virtual servers using FTP profiles
    Run 'tmsh list ltm virtual <virtual_name>' to check which virtual servers reference an FTP profile, or check via the Configuration Utility under Local Traffic > Virtual Servers
    Affected if A virtual server references an FTP profile with Active mode enabled
  5. Confirm virtual server is processing FTP traffic
    Monitor the virtual server statistics using 'tmsh show ltm virtual <virtual_name> stats' or check the FTP data channel connection status
    Affected if The virtual server is actively handling FTP connections and the FTP data channel stops responding after receiving the trigger traffic

The environment is affected if the BIG-IP version is one of the listed affected versions AND an Active mode-enabled FTP profile is attached to a virtual server handling FTP 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 F5 BIG-IP to patched versions (16.1.2.2, 15.1.5.1, 14.1.4.6, or 13.1.5) or temporarily disable Active mode FTP profiles on affected virtual servers if upgrading is not immediately feasible.

Recommended fix High confidence

For 13.1.x branch: upgrade to 13.1.5 or later | For 14.1.x branch: upgrade to 14.1.4.6 or later | For 15.1.x branch: upgrade to 15.1.5.1 or later | For 16.1.x branch: upgrade to 16.1.2.2 or later

  1. 1. Identify the current BIG-IP version by running 'tmsh show sys version' or checking the web UI (System > Software > Image/Volume)
  2. 2. Determine which version branch (13.1.x, 14.1.x, 15.1.x, or 16.1.x) your device is running
  3. 3. Download the appropriate fixed version ISO/image from the F5 downloads portal (downloads.f5.com)
  4. 4. Upload the new software version to the BIG-IP device via the web UI (Software > Image/Volume > Upload) or tmsh (upload sys software)
  5. 5. Install the new version by creating a new volume (Software > Volume > Create) and selecting the uploaded image
  6. 6. Boot into the new volume to activate the fixed version
  7. 7. Verify the version is running correctly: 'tmsh show sys version'
  8. 8. Test that FTP virtual servers with Active mode FTP profiles are processing connections properly
Caveat Upgrading BIG-IP software may cause brief service interruption; plan maintenance window. Verify compatibility of other modules and configurations after upgrade.

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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