dbcve.org
Big Ip Advanced Web Application FirewallApplication · F5

CVE-2025-58474

MEDIUM · 5.3 CVSS v3.1 Published 2025-10-15
Fix available
A fix is available. Upgrade to 17.1.2 or later.
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
When BIG-IP Advanced WAF is configured on a virtual server with Server-Side Request Forgery (SSRF) protection or when an NGINX server is configured with App Protect Bot Defense, undisclosed requests can disrupt new client requests.  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

This is a denial-of-service vulnerability where specifically crafted undisclosed requests, when BIG-IP Advanced WAF is configured with SSRF protection or NGINX has App Protect Bot Defense enabled, can disrupt processing of new client requests to affected virtual servers.

MitigationApply available patches or updates from F5 and NGINX for the affected products. If patches are unavailable, consider disabling SSRF protection temporarily or reviewing App Protect Bot Defense configuration to mitigate request disruption.

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 Advanced Web Application FirewallApplication
Affected:>= 17.1.0, < 17.1.2
Big Ip Application Security ManagerApplication
Affected:>= 17.1.0, < 17.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
    Retrieve the installed version of F5 BIG-IP Advanced WAF or Application Security Manager using the management interface or CLI command 'tmsh show sys version'. Compare the version number to the affected range: >= 17.1.0 and < 17.1.2.
    Affected if The installed version falls within 17.1.0 <= version < 17.1.2
  2. Confirm Advanced WAF module is licensed and provisioned
    Verify that the Advanced WAF (AWAF) module is provisioned on the BIG-IP system using 'tmsh list sys provision' or through the management console.
    Affected if Advanced WAF is provisioned and running
  3. Check if SSRF protection is enabled in the Advanced WAF policy
    Inspect the Application Security Manager policy configuration for the affected virtual server. Look for SSRF protection settings within the security policy. This can be viewed via the management UI under Security > Application Security > Policies or via tmsh command 'tmsh list apm policy' if SSRF protection is exposed there.
    Affected if SSRF protection is enabled and configured in the active security policy for any virtual server
  4. Check if NGINX App Protect Bot Defense is enabled
    If using NGINX Plus with App Protect, verify whether the Bot Defense module is loaded and active in the NGINX configuration. Look for 'app_protect_enable' directive or 'include /etc/nginx/nginx.conf;' referencing bot defense policy files.
    Affected if App Protect Bot Defense is enabled in the NGINX configuration for any served virtual server

You are affected if your BIG-IP version is between 17.1.0 and 17.1.2 (exclusive) AND either Advanced WAF with SSRF protection or NGINX with App Protect Bot Defense is actively protecting 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
Upgrade available Upgrade to 17.1.2 or later
Fixed in 17.1.2
Interim mitigation

Apply available patches or updates from F5 and NGINX for the affected products. If patches are unavailable, consider disabling SSRF protection temporarily or reviewing App Protect Bot Defense configuration to mitigate request disruption.

Recommended fix High confidence

BIG-IP 17.1.2 or later

  1. 1. Verify current BIG-IP version is in affected range (17.1.0 - 17.1.1) using 'tmsh show sys version' command
  2. 2. Review F5 release notes for version 17.1.2 for any known issues or special upgrade considerations
  3. 3. Schedule a maintenance window for the upgrade
  4. 4. Create a full backup of BIG-IP configuration using 'tmsh save sys config'
  5. 5. Download BIG-IP version 17.1.2 or later from F5 Downloads (my.f5.com)
  6. 6. Upload and install the upgrade via BIG-IP GUI (System > Software Management > ISO Image) or via tmsh
  7. 7. After reboot, verify the upgrade was successful and confirm WAF/ASM protection is functioning properly
Caveat Review F5 release notes for 17.1.2 for any known issues before upgrading; standard patch upgrade with minimal expected impact

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Big Ip Advanced Web Application Firewall Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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