dbcve.org
Big Ip Local Traffic ManagerApplication · F5

CVE-2017-6147

MEDIUM · 5.9 CVSS v3.0 Published 2017-09-18
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, Analytics, APM, ASM, DNS, Link Controller, PEM, and WebSafe 12.1.2-HF1 and 13.0.0, an undisclosed type of responses may cause TMM to restart, causing an interruption of service when "SSL Forward Proxy" setting is enabled in both the Client and Server SSL profiles assigned to a BIG-IP Virtual Server.

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 vulnerability in F5 BIG-IP allows an undisclosed type of response to trigger a TMM (Traffic Management Microkernel) restart when SSL Forward Proxy is enabled in both Client and Server SSL profiles on a virtual server, causing service interruption.

MitigationDisable SSL Forward Proxy in affected Client and Server SSL profiles, or upgrade to a patched version once available. Identify all virtual servers using this configuration and assess the business impact before making changes.

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.2= 13.0.0
Big Ip Application Acceleration ManagerApplication
Affected:= 12.1.2= 13.0.0
Big Ip Advanced Firewall ManagerApplication
Affected:= 12.1.2= 13.0.0
Big Ip AnalyticsApplication
Affected:= 12.1.2= 13.0.0
Big Ip Access Policy ManagerApplication
Affected:= 12.1.2= 13.0.0
Big Ip Application Security ManagerApplication
Affected:= 12.1.2= 13.0.0
Big Ip Domain Name SystemApplication
Affected:= 12.1.2= 13.0.0
Big Ip Link ControllerApplication
Affected:= 12.1.2= 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
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 version
    Run `tmsh show /sys version` or `tmsh list /sys version` to retrieve the installed version
    Affected if The version displayed is exactly 12.1.2 or 13.0.0 (note: other versions may also be affected but only these exact versions are listed as vulnerable)
  2. Identify Client SSL profiles with SSL Forward Proxy enabled
    Run `tmsh list /ltm profile client-ssl all` and look for the line `ssl forward proxy enabled` within each profile
    Affected if Any Client SSL profile has ssl forward proxy set to enabled
  3. Identify Server SSL profiles with SSL Forward Proxy enabled
    Run `tmsh list /ltm profile server-ssl all` and look for the line `ssl forward proxy enabled` within each profile
    Affected if Any Server SSL profile has ssl forward proxy set to enabled
  4. Check if vulnerable profile pairs are assigned to virtual servers
    Run `tmsh list /ltm virtual all` and examine which virtual servers have both a Client SSL and Server SSL profile assigned that both have ssl forward proxy enabled
    Affected if A virtual server references both a Client SSL profile and a Server SSL profile where each has ssl forward proxy enabled

A system is affected if it runs version 12.1.2 or 13.0.0 AND has at least one virtual server with both a Client SSL profile and a Server SSL profile that both have SSL Forward Proxy enabled.

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 SSL Forward Proxy in affected Client and Server SSL profiles, or upgrade to a patched version once available. Identify all virtual servers using this configuration and assess the business impact before making changes.

Fix this in Big Ip Local Traffic Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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