dbcve.org
Big Ip Application Security ManagerApplication · F5

CVE-2016-7472

HIGH · 7.5 CVSS v3.0 Published 2018-04-03
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
F5 BIG-IP ASM version 12.1.0 - 12.1.1 may allow remote attackers to cause a denial of service (DoS) via a crafted HTTP request.

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

A denial of service vulnerability exists in F5 BIG-IP ASM versions 12.1.0 through 12.1.1. Remote attackers can send specially crafted HTTP requests to trigger the DoS condition, potentially disrupting application security protection services.

MitigationUpgrade BIG-IP ASM to version 12.1.2 or later. If immediate patching is not possible, consider implementing additional upstream filtering or rate limiting to mitigate HTTP-based DoS attempts.

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 Application Security ManagerApplication
Affected:= 12.1.0= 12.1.1

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.0/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. Verify BIG-IP ASM is installed
    Run 'tmsh list sys software' or check the BIG-IP GUI under System > Software Management to see if ASM module is present
    Affected if ASM module is not listed in the installed software
  2. Check ASM version number
    Run 'tmsh show sys version' or access the GUI under iControl > System > Version Info. Locate the Application Security Manager version entry
    Affected if The ASM version shown is exactly 12.1.0 or 12.1.1
  3. Confirm ASM policy is active on virtual servers
    Run 'tmsh list ltm virtual' and check if any virtual server references an ASM policy (policy parameter points to an ASM policy name), or view virtual server settings in the GUI under Local Traffic > Virtual Servers
    Affected if At least one virtual server has an ASM security policy assigned and enabled
  4. Validate ASM module is provisioned
    Run 'tmsh show sys provision' or check System > Resource Provisioning in the GUI to confirm ASM is provisioned
    Affected if ASM shows as provisioned (not 'none' or unavailable)

You are affected if ASM version 12.1.0 or 12.1.1 is installed AND ASM is provisioned and actively protecting at least one virtual server with an ASM policy.

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

Upgrade BIG-IP ASM to version 12.1.2 or later. If immediate patching is not possible, consider implementing additional upstream filtering or rate limiting to mitigate HTTP-based DoS attempts.

Fix this in Big Ip Application Security Manager Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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