dbcve.org
Big Ip Advanced Firewall ManagerApplication · F5

CVE-2017-0304

MEDIUM · 5.4 CVSS v3.0 Published 2017-12-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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
A SQL injection vulnerability exists in the BIG-IP AFM management UI on versions 12.0.0, 12.1.0, 12.1.1, 12.1.2 and 13.0.0 that may allow a copy of the firewall rules to be tampered with and impact the Configuration Utility until there is a resync of the rules. Traffic processing and the live firewall rules in use are not affected.

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

SQL injection vulnerability in the BIG-IP AFM (Advanced Firewall Manager) management UI allows authenticated attackers to tamper with copies of firewall rules within the Configuration Utility. The attack affects only the management interface and the rule copies, not the live traffic processing or active firewall rules.

MitigationApply the appropriate F5 hotfix or upgrade to a fixed version as specified in F5 security advisory. Since this is a management-plane vulnerability, prioritize patching during a scheduled maintenance window.

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 Firewall ManagerApplication
Affected:= 12.0.0= 12.1.0= 12.1.1= 12.1.2= 13.0.0

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/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. Confirm BIG-IP AFM is installed
    Log into the BIG-IP management UI or run 'tmsh show sys module' command to list installed modules. Look for 'afm' (Advanced Firewall Manager) in the module list.
    Affected if The Advanced Firewall Manager (afm) module is not installed on the system.
  2. Check the BIG-IP version
    Run 'tmsh show sys version' or access the management UI and check System > About. Record the exact version number.
    Affected if The installed version is 12.0.0, 12.1.0, 12.1.1, 12.1.2, or 13.0.0 exactly.
  3. Verify management interface accessibility
    Check if the BIG-IP Configuration Utility (management UI on port 443 or 8443) is accessible from network locations beyond the trusted administrative network. Review management interface bindings in 'tmsh list sys httpd' and network ACLs.
    Affected if The management interface is exposed to untrusted networks and the affected version is running.
  4. Review management user access
    Audit the list of users with access to the Configuration Utility by checking 'tmsh list auth user' or the GUI under User Management. Identify any accounts that could be compromised.
    Affected if Multiple or untrusted users have authenticated access to the management UI on an affected version.

You are affected if BIG-IP AFM is installed AND the version matches exactly 12.0.0, 12.1.0, 12.1.1, 12.1.2, or 13.0.0 AND the management interface is accessible to authenticated users (even privileged ones) in your environment.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the appropriate F5 hotfix or upgrade to a fixed version as specified in F5 security advisory. Since this is a management-plane vulnerability, prioritize patching during a scheduled maintenance window.

Fix this in Big Ip Advanced Firewall Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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