dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2024-33604

MEDIUM · 6.1 CVSS v3.1 Published 2024-05-08
Fix available
A fix is available. Upgrade to 15.1.10.4 / 16.1.4.3 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
A reflected cross-site scripting (XSS) vulnerability exist in undisclosed page of the BIG-IP Configuration utility that allows an attacker to run JavaScript in the context of the currently logged-in user.  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

Reflected cross-site scripting (XSS) vulnerability in an undisclosed page of F5 BIG-IP Configuration utility. Attackers can inject malicious JavaScript via crafted URLs that executes in the context of the victim's active session, potentially allowing session hijacking or actions as the logged-in user.

MitigationApply the F5 security update for CVE-2024-33604 when available. Until then, implement URL filtering and monitor for suspicious links targeting BIG-IP interfaces, as this is a reflected XSS requiring user interaction.

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:>= 15.1.0, < 15.1.10.4>= 16.1.0, < 16.1.4.3>= 17.1.0, < 17.1.1.3
Big Ip Advanced Firewall ManagerApplication
Affected:>= 15.1.0, < 15.1.10.4>= 16.1.0, < 16.1.4.3>= 17.1.0, < 17.1.1.3
Big Ip Advanced Web Application FirewallApplication
Affected:>= 15.1.0, < 15.1.10.4>= 16.1.0, < 16.1.4.3>= 17.1.0, < 17.1.1.3
Big Ip AnalyticsApplication
Affected:>= 15.1.0, < 15.1.10.4>= 16.1.0, < 16.1.4.3>= 17.1.0, < 17.1.1.3
Big Ip Application Acceleration ManagerApplication
Affected:>= 15.1.0, < 15.1.10.4>= 16.1.0, < 16.1.4.3>= 17.1.0, < 17.1.1.3
Big Ip Application Security ManagerApplication
Affected:>= 15.1.0, < 15.1.10.4>= 16.1.0, < 16.1.4.3>= 17.1.0, < 17.1.1.3
Big Ip Application Visibility And ReportingApplication
Affected:>= 15.1.0, < 15.1.10.4>= 16.1.0, < 16.1.4.3>= 17.1.0, < 17.1.1.3
Big Ip Automation ToolchainApplication
Affected:>= 15.1.0, < 15.1.10.4>= 16.1.0, < 16.1.4.3>= 17.1.0, < 17.1.1.3

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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. Identify BIG-IP base version
    Run command: tmsh show sys version | grep -i version or access System > Software Management > ISO Image in the GUI
    Affected if Version falls within 15.1.0-15.1.10.3, 16.1.0-16.1.4.2, or 17.1.0-17.1.1.2
  2. Confirm affected module versions
    Check each installed module version via tmsh: tmsh list sys software volume <volume-name> | grep -i version, or view in GUI under System > Software Management
    Affected if Any BIG-IP module (APM, AFM, ASM, Analytics, AAM, ASM, AVR, Automation Toolchain) matches the affected version ranges
  3. Verify Configuration utility exposure
    Review network access restrictions: tmsh list sys httpd all-procs or check iRule/Policy restrictions for management interface access
    Affected if The Configuration utility (management GUI) is accessible from untrusted networks without proper access controls
  4. Examine access logs for suspicious URLs
    Review /var/log/httpd/tmui.log for unusual query parameters, especially on the undisclosed affected page. Use: grep -E '\?.*=' /var/log/httpd/tmui.log | head -100
    Affected if Logs show crafted URLs with script injection patterns (such as <script> tags, javascript: URLs, or event handlers in query parameters)

If the BIG-IP version falls within 15.1.0-15.1.10.3, 16.1.0-16.1.4.2, or 17.1.0-17.1.1.2 AND the Configuration utility is accessible to potential attackers, the environment is vulnerable to reflected XSS via crafted URLs.

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 15.1.10.4 / 16.1.4.3 / 17.1.1.3 or later
Fixed in 15.1.10.416.1.4.317.1.1.3
Interim mitigation

Apply the F5 security update for CVE-2024-33604 when available. Until then, implement URL filtering and monitor for suspicious links targeting BIG-IP interfaces, as this is a reflected XSS requiring user interaction.

Recommended fix High confidence

Upgrade to 15.1.10.4+, 16.1.4.3+, or 17.1.1.3+ depending on your current major version branch

  1. 1. Identify the current BIG-IP version by checking System > Software Management > ISO Image or using 'tmsh show sys version'
  2. 2. Determine which version branch (15.1.x, 16.1.x, or 17.1.x) is currently deployed
  3. 3. Download the appropriate fixed version ISO from F5 Networks: 15.1.10.4 (or later 15.1.x), 16.1.4.3 (or later 16.1.x), or 17.1.1.3 (or later 17.1.x)
  4. 4. Upload the new software image to the BIG-IP device via System > Software Management > ISO Image
  5. 5. Create a new volume for the upgrade via System > Software Management > Volume
  6. 6. Install the new software version to the volume
  7. 7. Reboot the BIG-IP device to boot from the new volume
  8. 8. Verify the upgrade was successful by checking System > Software Management > Volume status and confirming the version number
Caveat Major version upgrades may require careful planning; review F5 upgrade guides for potential configuration compatibility considerations and ensure adequate downtime window

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
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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