dbcve.org
Big Ip Local Traffic ManagerApplication · F5

CVE-2017-6132

HIGH · 7.5 CVSS v3.0 Published 2017-12-21
Fix available
A fix is available. Upgrade to after 12.1.2 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
In F5 BIG-IP LTM, AAM, AFM, Analytics, APM, ASM, DNS, GTM, Link Controller, PEM and Websafe software version 13.0.0, 12.0.0 to 12.1.2, 11.6.0 to 11.6.1 and 11.5.0 - 11.5.4, an undisclosed sequence of packets sent to BIG-IP High Availability state mirror listeners (primary and/or secondary IP) may cause TMM to restart.

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

A denial of service vulnerability in F5 BIG-IP allows remote attackers to cause the Traffic Management Microkernel (TMM) to restart by sending an undisclosed sequence of packets to High Availability state mirror listeners (primary and/or secondary HA IPs). This affects multiple BIG-IP modules including LTM, ASM, APM, DNS, and others.

MitigationApply the relevant F5 hotfix or upgrade to a patched version as specified in F5's security advisory. For immediate workarounds, consider restricting access to HA state mirror listener ports or implementing additional network segmentation.

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.6.0, <= 11.6.1>= 12.0.0, <= 12.1.2= 11.5.0= 11.5.1= 11.5.2= 11.5.3= 11.5.4= 13.0.0
Big Ip Application Acceleration ManagerApplication
Affected:>= 11.6.0, <= 11.6.1>= 12.0.0, <= 12.1.2= 11.5.0= 11.5.1= 11.5.2= 11.5.3= 11.5.4= 13.0.0
Big Ip Advanced Firewall ManagerApplication
Affected:>= 11.6.0, <= 11.6.1>= 12.0.0, <= 12.1.2= 11.5.0= 11.5.1= 11.5.2= 11.5.3= 11.5.4= 13.0.0
Big Ip AnalyticsApplication
Affected:>= 11.6.0, <= 11.6.1>= 12.0.0, <= 12.1.2= 11.5.0= 11.5.1= 11.5.2= 11.5.3= 11.5.4= 13.0.0
Big Ip Access Policy ManagerApplication
Affected:>= 11.6.0, <= 11.6.1>= 12.0.0, <= 12.1.2= 11.5.0= 11.5.1= 11.5.2= 11.5.3= 11.5.4= 13.0.0
Big Ip Application Security ManagerApplication
Affected:>= 11.6.0, <= 11.6.1>= 12.0.0, <= 12.1.2= 11.5.0= 11.5.1= 11.5.2= 11.5.3= 11.5.4= 13.0.0
Big Ip DnsApplication
Affected:>= 11.6.0, <= 11.6.1>= 12.0.0, <= 12.1.2= 11.5.0= 11.5.1= 11.5.2= 11.5.3= 11.5.4= 13.0.0
Big Ip Global Traffic ManagerApplication
Affected:>= 11.6.0, <= 11.6.1>= 12.0.0, <= 12.1.2= 11.5.0= 11.5.1= 11.5.2= 11.5.3= 11.5.4= 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. Identify BIG-IP version
    Run the command 'tmsh show sys version' or check the BIG-IP web UI under System > Software > Image . The version will be displayed in the output.
    Affected if The installed version matches any of these ranges: 11.5.0-11.5.4, 11.6.0-11.6.1, 12.0.0-12.1.2, or 13.0.0 exactly.
  2. Verify High Availability is configured
    Check if the device is part of an HA pair by running 'tmsh show sys ha-status' or viewing the Device Trust and Failover settings in the web UI under Device Management.
    Affected if HA is enabled and the device has a peer device configured for failover.
  3. Confirm HA state mirror listener is active
    Run 'tmsh list sys ha' to view HA configuration, and check for mirror listener settings on the primary and/or secondary HA IP addresses. In the web UI, review Network > HA Mirroring settings.
    Affected if HA state mirror listeners are configured on primary and/or secondary HA IPs.
  4. Assess network exposure of HA ports
    Review firewall rules and network access lists to determine if the HA mirror ports (port 1026 and 1027 by default for state mirroring) are exposed to untrusted networks. Use 'tmsh show sys ha-mirror' to list active mirror addresses.
    Affected if The HA mirror listener ports are reachable from networks outside the trusted management or HA-only network segment.

You are affected if your BIG-IP version is 11.5.0-11.5.4, 11.6.0-11.6.1, 12.0.0-12.1.2, or 13.0.0 AND HA with state mirror listeners is enabled AND the HA mirror ports are network-accessible to remote attackers.

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 the relevant F5 hotfix or upgrade to a patched version as specified in F5's security advisory. For immediate workarounds, consider restricting access to HA state mirror listener ports or implementing additional network segmentation.

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