dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2017-6141

MEDIUM · 5.9 CVSS v3.0 Published 2017-10-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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, APM, ASM, Link Controller, PEM, and WebSafe 12.1.0 through 12.1.2, certain values in a TLS abbreviated handshake when using a client SSL profile with the Session Ticket option enabled may cause disruption of service to the Traffic Management Microkernel (TMM). The Session Ticket option is disabled by default.

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

F5 BIG-IP products running 12.1.0-12.1.2 contain a denial-of-service vulnerability in the Traffic Management Microkernel (TMM). When a client SSL profile has the Session Ticket option enabled, certain malformed values in TLS abbreviated handshakes can cause TMM to crash or become unavailable.

MitigationDisable the Session Ticket option in client SSL profiles (it is disabled by default), or upgrade to a patched BIG-IP version. Verify that Session Ticket is not enabled on production SSL profiles.

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:= 12.1.0= 12.1.1= 12.1.2
Big Ip Advanced Firewall ManagerApplication
Affected:= 12.1.0= 12.1.1= 12.1.2
Big Ip Application Acceleration ManagerApplication
Affected:= 12.1.0= 12.1.1= 12.1.2
Big Ip Application Security ManagerApplication
Affected:= 12.1.0= 12.1.1= 12.1.2
Big Ip Link ControllerApplication
Affected:= 12.1.0= 12.1.1= 12.1.2
Big Ip Local Traffic ManagerApplication
Affected:= 12.1.0= 12.1.1= 12.1.2
Big Ip Policy Enforcement ManagerApplication
Affected:= 12.1.0= 12.1.1= 12.1.2
Big Ip WebsafeApplication
Affected:= 12.1.0= 12.1.1= 12.1.2

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. Identify BIG-IP version
    Run 'tmsh show sys version' or check the web UI under System > Software > Image
    Affected if The version is 12.1.0, 12.1.1, or 12.1.2
  2. Locate client SSL profiles
    Run 'tmsh list ltm profile client-ssl' to list all client SSL profiles configured on the system
    Affected if Any client SSL profiles exist on the device
  3. Check Session Ticket status
    For each client SSL profile, run 'tmsh list ltm profile client-ssl <profile_name>' and inspect the 'session-ticket enabled' setting
    Affected if Session Ticket is set to enabled (not disabled) on any client SSL profile
  4. Verify TLS configuration exposure
    Confirm the profile is attached to a virtual server by running 'tmsh list ltm virtual <virtual_name>' and checking the client-ssl profile reference
    Affected if A client SSL profile with Session Ticket enabled is associated with an active virtual server

The environment is affected if the BIG-IP version is 12.1.0, 12.1.1, or 12.1.2 AND any client SSL profile has Session Ticket enabled and is in use.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable the Session Ticket option in client SSL profiles (it is disabled by default), or upgrade to a patched BIG-IP version. Verify that Session Ticket is not enabled on production SSL profiles.

Fix this in Big Ip Access Policy Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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