dbcve.org
Big Ip Local Traffic ManagerApplication · F5

CVE-2017-6162

MEDIUM · 5.9 CVSS v3.0 Published 2017-10-27
Fix available
A fix is available. Upgrade to after 11.5.4 or later.
See remediation →
68/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
In F5 BIG-IP LTM, AAM, AFM, Analytics, APM, ASM, DNS, Edge Gateway, GTM, Link Controller, PEM, Websafe software version 12.0.0 to 12.1.2, 11.6.0 to 11.6.1, 11.4.0 to 11.5.4, 11.2.1, in some cases TMM may crash when processing TCP traffic. This vulnerability affects TMM via a virtual server configured with TCP profile. Traffic processing is disrupted while Traffic Management Microkernel (TMM) restarts. If the affected BIG-IP system is configured to be part of a device group, it will trigger a failover to the peer device.

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 crash vulnerability exists in F5 BIG-IP TMM (Traffic Management Microkernel) when processing TCP traffic through virtual servers configured with a TCP profile. The vulnerability affects multiple BIG-IP modules (LTM, ASM, APM, DNS, etc.) across versions 11.2.1 through 12.1.2, causing TMM to crash and restart, disrupting traffic processing.

MitigationUpgrade to a patched version of BIG-IP software; alternatively, review and potentially disable or reconfigure affected virtual servers with TCP profiles until patching can be completed.

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 Local Traffic ManagerApplication
Affected:>= 11.5.0, <= 11.5.4= 11.2.1= 11.6.0= 11.6.1= 12.0.0= 12.1.0= 12.1.1
Big Ip Application Acceleration ManagerApplication
Affected:>= 11.5.0, <= 11.5.4= 11.2.1= 11.6.0= 11.6.1= 12.0.0= 12.1.0= 12.1.1
Big Ip Advanced Firewall ManagerApplication
Affected:>= 11.5.0, <= 11.5.4= 11.2.1= 11.6.0= 11.6.1= 12.0.0= 12.1.0= 12.1.1
Big Ip Access Policy ManagerApplication
Affected:>= 11.5.0, <= 11.5.4= 11.2.1= 11.6.0= 11.6.1= 12.0.0= 12.1.0= 12.1.1
Big Ip Application Security ManagerApplication
Affected:>= 11.5.0, <= 11.5.4= 11.2.1= 11.6.0= 11.6.1= 12.0.0= 12.1.0= 12.1.1
Big Ip Link ControllerApplication
Affected:>= 11.5.0, <= 11.5.4= 11.2.1= 11.6.0= 11.6.1= 12.0.0= 12.1.0= 12.1.1
Big Ip Policy Enforcement ManagerApplication
Affected:>= 11.5.0, <= 11.5.4= 11.2.1= 11.6.0= 11.6.1= 12.0.0= 12.1.0= 12.1.1
Big Ip WebsafeApplication
Affected:= 1.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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:H/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. Check BIG-IP software version
    Run `tmsh show sys version` or `bigstart status` to determine the installed BIG-IP version
    Affected if Version is 11.2.1, 11.5.0-11.5.4, 11.6.0, 11.6.1, 12.0.0, 12.1.0, or 12.1.1
  2. Identify virtual servers with TCP profiles
    Run `tmsh list ltm virtual all` and look for the `tcp` profile referenced in each virtual server configuration
    Affected if Any virtual server references a TCP profile in its configuration
  3. Check for TMM crashes
    Review TMM crash logs with `tmsh show ltm crash` or check `/var/log/ltm` for TMM restart entries
    Affected if TMM has crashed or restarted unexpectedly
  4. Verify affected module is provisioned
    Run `tmsh show sys provision` to see which modules (LTM, ASM, APM, DNS, AAM, AFM, PEM, WebSafe) are provisioned
    Affected if Any affected module is provisioned on the system
  5. Confirm virtual servers are processing traffic
    Run `tmsh show ltm virtual` to see active connections and statistics on virtual servers
    Affected if Virtual servers with TCP profiles are actively processing TCP traffic

Your environment is affected if you are running a listed vulnerable version, have provisioned any affected module, and operate virtual servers configured with TCP profiles that handle TCP 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.

From vendor data
Upgrade available Upgrade to a release after 11.5.4
Interim mitigation

Upgrade to a patched version of BIG-IP software; alternatively, review and potentially disable or reconfigure affected virtual servers with TCP profiles until patching can be completed.

Fix this in Big Ip Local Traffic Manager 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-2017-6162 — 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-6162 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