dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2016-7475

HIGH · 7.5 CVSS v3.0 Published 2018-10-08
Fix available
A fix is available. Upgrade to after 12.1.0 or later.
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
Under some circumstances on BIG-IP 12.0.0-12.1.0, 11.6.0-11.6.1, or 11.4.0-11.5.4 HF1, the Traffic Management Microkernel (TMM) may not properly clean-up pool member network connections when using SPDY or HTTP/2 virtual server profiles.

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

In F5 BIG-IP devices running versions 12.0.0-12.1.0, 11.6.0-11.6.1, or 11.4.0-11.5.4 HF1, the Traffic Management Microkernel (TMM) fails to properly clean up pool member network connections when SPDY or HTTP/2 virtual server profiles are in use, potentially causing resource exhaustion or connection leaks.

MitigationUpgrade BIG-IP to a version beyond the affected ranges (12.1.1+ or 11.6.2+ or 11.5.4 HF2+). Prior to upgrade, identify and inventory all virtual servers using SPDY/HTTP2 profiles to assess exposure scope.

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:>= 11.4.0, <= 11.6.1>= 12.0.0, <= 12.1.0
Big Ip Advanced Firewall ManagerApplication
Affected:>= 11.4.0, <= 11.6.1>= 12.0.0, <= 12.1.0
Big Ip Application Acceleration ManagerApplication
Affected:>= 11.4.0, <= 11.6.1>= 12.0.0, <= 12.1.0
Big Ip Application Security ManagerApplication
Affected:>= 11.4.0, <= 11.6.1>= 12.0.0, <= 12.1.0
Big Ip Link ControllerApplication
Affected:>= 11.4.0, <= 11.6.1>= 12.0.0, <= 12.1.0
Big Ip Local Traffic ManagerApplication
Affected:>= 11.4.0, <= 11.6.1>= 12.0.0, <= 12.1.0
Big Ip Policy Enforcement ManagerApplication
Affected:>= 11.4.0, <= 11.6.1>= 12.0.0, <= 12.1.0
Big Ip Protocol Security ModulePlugin / extension
Affected:>= 11.4.0, <= 11.4.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. Identify BIG-IP version
    Run 'tmsh show sys version' or check the web UI under System > Software > Version
    Affected if Version is 12.0.0-12.1.0, 11.6.0-11.6.1, or 11.4.0-11.5.4 HF1
  2. List virtual servers with SPDY profiles
    Run 'tmsh list ltm virtual profile' and look for spdy profile references, or inspect virtual server configuration via web UI under Local Traffic > Virtual Servers
    Affected if Any virtual server has a SPDY profile attached
  3. List virtual servers with HTTP/2 profiles
    Run 'tmsh list ltm virtual profile' and look for http/2 profile references, or inspect virtual server configuration via web UI under Local Traffic > Virtual Servers
    Affected if Any virtual server has an HTTP/2 profile attached
  4. Check for connection accumulation
    Monitor TMM connection tables via 'tmsh show ltm tmm-connection' or 'tmsh show ltm pool <pool-name> members' over time for unexpected growth
    Affected if Pool member connections continuously increase without recycling or cleanup

A system is affected if it runs a vulnerable BIG-IP version AND has SPDY or HTTP/2 profiles configured on any virtual servers, potentially showing connection leaks in pool member stats.

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
Upgrade available Upgrade to a release after 12.1.0
Interim mitigation

Upgrade BIG-IP to a version beyond the affected ranges (12.1.1+ or 11.6.2+ or 11.5.4 HF2+). Prior to upgrade, identify and inventory all virtual servers using SPDY/HTTP2 profiles to assess exposure scope.

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-2016-7475 — 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-7475 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