dbcve.org
Big Ip Local Traffic ManagerApplication · F5

CVE-2017-6150

HIGH · 7.5 CVSS v3.0 Published 2018-03-01
Fix available
A fix is available. Upgrade to after 12.1.3.1 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 certain conditions for F5 BIG-IP systems 13.0.0 or 12.1.0 - 12.1.3.1, using FastL4 profiles, when the Reassemble IP Fragments option is disabled (default), some specific large fragmented packets may restart the Traffic Management Microkernel (TMM).

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 systems 13.0.0 and 12.1.0-12.1.3.1, when using FastL4 profiles with the Reassemble IP Fragments option disabled (the default), certain large fragmented packets can trigger a restart of the Traffic Management Microkernel (TMM), causing denial of service.

MitigationEnable the Reassemble IP Fragments option in affected FastL4 profiles, or upgrade to a patched BIG-IP version that addresses this vulnerability.

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:>= 12.1.0, <= 12.1.3.1= 13.0.0
Big Ip Application Acceleration ManagerApplication
Affected:>= 12.1.0, <= 12.1.3.1= 13.0.0
Big Ip Advanced Firewall ManagerApplication
Affected:>= 12.1.0, <= 12.1.3.1= 13.0.0
Big Ip AnalyticsApplication
Affected:>= 12.1.0, <= 12.1.3.1= 13.0.0
Big Ip Access Policy ManagerApplication
Affected:>= 12.1.0, <= 12.1.3.1= 13.0.0
Big Ip Application Security ManagerApplication
Affected:>= 12.1.0, <= 12.1.3.1= 13.0.0
Big Ip DnsApplication
Affected:>= 12.1.0, <= 12.1.3.1= 13.0.0
Big Ip Link ControllerApplication
Affected:>= 12.1.0, <= 12.1.3.1= 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
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. Check BIG-IP version
    Run `tmsh show sys version` or `tmsh show sys hardware` to identify the installed BIG-IP version
    Affected if The version is 12.1.0 through 12.1.3.1, or exactly 13.0.0
  2. Identify FastL4 profiles in use
    Run `tmsh list ltm profile fastl4` to list all configured FastL4 profiles on the system
    Affected if Any FastL4 profiles exist on the system (they are vulnerable by default)
  3. Verify Reassemble IP Fragments setting
    For each FastL4 profile, run `tmsh list ltm profile fastl4 <profile_name>` and check if `reassemble-ip-fragments` is set to `disabled` or not explicitly set (defaults to disabled)
    Affected if The Reassemble IP Fragments option is disabled or not explicitly enabled in the FastL4 profile

The system is affected if it runs BIG-IP version 12.1.0-12.1.3.1 or 13.0.0 AND has any FastL4 profiles with the Reassemble IP Fragments option disabled (the default setting).

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

Enable the Reassemble IP Fragments option in affected FastL4 profiles, or upgrade to a patched BIG-IP version that addresses this vulnerability.

Fix this in Big Ip Local Traffic Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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