dbcve.org
Big Ip Local Traffic ManagerApplication · F5

CVE-2017-6158

MEDIUM · 6.5 CVSS v3.0 Published 2018-04-13
Fix available
A fix is available. Upgrade to after 12.1.2 or later.
See remediation →
74/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 12.0.0-12.1.2, 11.6.0-11.6.1, 11.5.1-11.5.5, or 11.2.1 there is a vulnerability in TMM related to handling of invalid IP addresses.

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

Vulnerability in F5 BIG-IP's TMM (Traffic Management Microkernel) where improper handling of invalid IP addresses in network traffic can lead to a security issue. The flaw exists in specific versions of BIG-IP across multiple release branches.

MitigationApply vendor-supplied patch/upgrade to a BIG-IP version beyond 12.1.2 (for 12.x branch), 11.6.1 (for 11.6.x), 11.5.5 (for 11.5.x), or 11.2.1 (for 11.2.x) as specified in F5 security advisory.

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.1, <= 11.5.5>= 11.6.0, <= 11.6.1>= 12.0.0, <= 12.1.2= 11.2.1
Big Ip Application Acceleration ManagerApplication
Affected:>= 11.5.1, <= 11.5.5>= 11.6.0, <= 11.6.1>= 12.0.0, <= 12.1.2= 11.2.1
Big Ip Advanced Firewall ManagerApplication
Affected:>= 11.5.1, <= 11.5.5>= 11.6.0, <= 11.6.1>= 12.0.0, <= 12.1.2= 11.2.1
Big Ip AnalyticsApplication
Affected:>= 11.5.1, <= 11.5.5>= 11.6.0, <= 11.6.1>= 12.0.0, <= 12.1.2= 11.2.1
Big Ip Access Policy ManagerApplication
Affected:>= 11.5.1, <= 11.5.5>= 11.6.0, <= 11.6.1>= 12.0.0, <= 12.1.2= 11.2.1
Big Ip Application Security ManagerApplication
Affected:>= 11.5.1, <= 11.5.5>= 11.6.0, <= 11.6.1>= 12.0.0, <= 12.1.2= 11.2.1
Big Ip Edge GatewayWeb browser
Affected:>= 11.5.1, <= 11.5.5>= 11.6.0, <= 11.6.1>= 12.0.0, <= 12.1.2= 11.2.1
Big Ip Global Traffic ManagerApplication
Affected:>= 11.5.1, <= 11.5.5>= 11.6.0, <= 11.6.1>= 12.0.0, <= 12.1.2= 11.2.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
Low
Availability
Low

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

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. Determine BIG-IP base version
    Run 'tmsh show sys version' or check the login splash screen. On the command line, execute 'bigpipe version' or inspect /etc/product_version.
    Affected if The version falls within 11.2.1, 11.5.1-11.5.5, 11.6.0-11.6.1, or 12.0.0-12.1.2.
  2. Identify enabled modules
    Run 'tmsh list sys module' to list all installed and enabled BIG-IP modules. Alternatively, check 'tmsh show sys module' for module status.
    Affected if Any of these modules are enabled: Local Traffic Manager (LTM), Application Acceleration Manager (AAM), Advanced Firewall Manager (AFM), Analytics, Access Policy Manager (APM), Application Security Manager (ASM), Edge Gateway, or Global Traffic Manager (GTM).
  3. Confirm TMM is active
    Run 'tmsh show tmm' to verify the Traffic Management Microkernel is running. TMM is the component with the vulnerability.
    Affected if TMM is running, which is the default state for any BIG-IP system with traffic processing enabled.
  4. Compare against affected version ranges
    Cross-reference the identified BIG-IP version with the affected ranges: 11.2.1, 11.5.1-11.5.5, 11.6.0-11.6.1, or 12.0.0-12.1.2.
    Affected if The installed version exactly matches one of the affected versions or falls within one of the affected ranges.

If the BIG-IP version is 11.2.1, 11.5.1-11.5.5, 11.6.0-11.6.1, or 12.0.0-12.1.2 AND any traffic management module (LTM, AAM, AFM, APM, ASM, GTM, Edge Gateway, or Analytics) is enabled, the environment is affected by this CVE.

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.2
Interim mitigation

Apply vendor-supplied patch/upgrade to a BIG-IP version beyond 12.1.2 (for 12.x branch), 11.6.1 (for 11.6.x), 11.5.5 (for 11.5.x), or 11.2.1 (for 11.2.x) as specified in F5 security advisory.

Fix this in Big Ip Local Traffic Manager Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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