dbcve.org
Big Ip Local Traffic ManagerApplication · F5

CVE-2017-6157

HIGH · 8.1 CVSS v3.0 Published 2017-10-27
Fix available
A fix is available. Upgrade to after 11.5.4 or later.
See remediation →
90/100
Remediation priority · Urgent
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 12.0.0 to 12.1.1, 11.6.0 to 11.6.1, 11.5.0 - 11.5.4, virtual servers with a configuration using the HTTP Explicit Proxy functionality and/or SOCKS profile are vulnerable to an unauthenticated, remote attack that allows modification of BIG-IP system configuration, extraction of sensitive system files, and/or possible remote command execution on the BIG-IP system.

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

F5 BIG-IP vulnerability in the HTTP Explicit Proxy and SOCKS profile functionality allows unauthenticated remote attackers to modify system configuration, extract sensitive files, or execute commands on the BIG-IP system.

MitigationUpgrade to a patched F5 BIG-IP version or disable HTTP Explicit Proxy and SOCKS profile configurations on affected virtual servers if not required.

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.0, <= 11.5.4= 11.6.0= 11.6.1= 12.0.0= 12.1.0= 12.1.1
Big Ip Application Acceleration ManagerApplication
Affected:>= 11.5.0, <= 11.5.4= 11.6.0= 11.6.1= 12.0.0= 12.1.0= 12.1.1
Big Ip Advanced Firewall ManagerApplication
Affected:>= 11.5.0, <= 11.5.4= 11.6.0= 11.6.1= 12.0.0= 12.1.0= 12.1.1
Big Ip Access Policy ManagerApplication
Affected:>= 11.5.0, <= 11.5.4= 11.6.0= 11.6.1= 12.0.0= 12.1.0= 12.1.1
Big Ip Application Security ManagerApplication
Affected:>= 11.5.0, <= 11.5.4= 11.6.0= 11.6.1= 12.0.0= 12.1.0= 12.1.1
Big Ip Link ControllerApplication
Affected:>= 11.5.0, <= 11.5.4= 11.6.0= 11.6.1= 12.0.0= 12.1.0= 12.1.1
Big Ip Policy Enforcement ManagerApplication
Affected:>= 11.5.0, <= 11.5.4= 11.6.0= 11.6.1= 12.0.0= 12.1.0= 12.1.1
Big Ip WebsafeApplication
Affected:= 11.6.0= 11.6.1= 12.0.0= 12.1.0= 12.1.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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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 the F5 BIG-IP version
    Run `tmsh show sys version` on the command line, or log into the web UI and check System > Software Management > Install
    Affected if The installed version falls within 11.5.0-11.5.4, 11.6.0, 11.6.1, 12.0.0, 12.1.0, or 12.1.1
  2. List installed BIG-IP modules
    Run `tmsh list sys module` to see which modules are licensed and loaded, or check the web UI under System > Services
    Affected if Any of the following modules are installed: LTM, AAM, AFM, APM, ASM, Link Controller, PEM, or Websafe on an affected version
  3. Check for HTTP Explicit Proxy configuration
    Run `tmsh list ltm explicit-proxy` to see if an explicit proxy is defined, or in the web UI navigate to Local Traffic > Profiles > Explicit Proxy
    Affected if An explicit proxy profile is created and assigned to a virtual server
  4. Check for SOCKS profile configuration
    Run `tmsh list ltm socks` to list any SOCKS profiles, or in the web UI check Local Traffic > Profiles > SOCKS
    Affected if A SOCKS profile exists and is applied to a virtual server

A system is affected if it runs any of the listed BIG-IP versions with either an HTTP Explicit Proxy or SOCKS profile configured and enabled on a virtual server.

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 11.5.4
Interim mitigation

Upgrade to a patched F5 BIG-IP version or disable HTTP Explicit Proxy and SOCKS profile configurations on affected virtual servers if not required.

Fix this in Big Ip Local Traffic Manager Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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