dbcve.org
Ssl Intercept IappApplication · F5

CVE-2017-6130

HIGH · 7.4 CVSS v3.0 Published 2017-04-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges

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
F5 SSL Intercept iApp 1.5.0 - 1.5.7 and SSL Orchestrator 2.0 is vulnerable to a Server-Side Request Forgery (SSRF) attack when deployed using the Dynamic Domain Bypass (DDB) feature feature plus SNAT Auto Map option for egress traffic.

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 SSL Intercept iApp versions 1.5.0 through 1.5.7 and SSL Orchestrator 2.0 contain a Server-Side Request Forgery (SSRF) vulnerability when the Dynamic Domain Bypass (DDB) feature is used in combination with the SNAT Auto Map option for egress traffic, allowing attackers to induce the F5 device to make unintended requests to arbitrary internal or external systems.

MitigationDisable either the Dynamic Domain Bypass (DDB) feature or the SNAT Auto Map option to eliminate the SSRF attack surface, or upgrade to a patched version if available from F5.

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
Ssl Intercept IappApplication
Affected:= 1.5.0= 1.5.7
Ssl OrchestratorApplication
Affected:= 2.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
Required
Scope
Changed
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N

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 installed F5 product
    Check if F5 SSL Intercept iApp or F5 SSL Orchestrator is deployed on the F5 device. This can be verified in the iApp menu or by reviewing the installed packages via tmsh: 'tmsh list sys app service'
    Affected if The product is SSL Intercept iApp or SSL Orchestrator
  2. Determine the SSL Intercept iApp version
    Run 'tmsh list sys app service <service_name>' to view the configuration and identify the iApp version. For SSL Orchestrator, check the version in the SSL Orchestrator UI or via 'tmsh list sys app service sslo*'
    Affected if Version is 1.5.0 through 1.5.7 for SSL Intercept iApp, or version 2.0 for SSL Orchestrator
  3. Verify if Dynamic Domain Bypass (DDB) is enabled
    In the SSL Intercept iApp or SSL Orchestrator configuration, locate the DDB settings. This is typically found under the iApp template options for domain bypass. Check the configuration via tmsh or the web UI for any defined bypass domains.
    Affected if DDB feature is actively configured and enabled in the iApp or SSL Orchestrator configuration
  4. Confirm SNAT Auto Map is in use for egress traffic
    Examine the traffic management configuration for the virtual server associated with SSL Intercept. Check the SNAT configuration: 'tmsh list ltm virtual <virtual_name>' and look for 'snat automap' in the source address translation settings.
    Affected if SNAT Auto Map is explicitly enabled for the SSL Intercept virtual server egress traffic

The environment is affected only if the product version is 1.5.0-1.5.7 (SSL Intercept iApp) or 2.0 (SSL Orchestrator) AND both Dynamic Domain Bypass AND SNAT Auto Map are simultaneously 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 either the Dynamic Domain Bypass (DDB) feature or the SNAT Auto Map option to eliminate the SSRF attack surface, or upgrade to a patched version if available from F5.

Fix this in Ssl Intercept Iapp Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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