dbcve.org
Ssl Intercept IappApplication · F5

CVE-2017-0305

CRITICAL · 9.8 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 →
100/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
F5 SSL Intercept iApp version 1.5.0 - 1.5.7 is vulnerable to an unauthenticated, remote attack that may allow modification of the BIG-IP system configuration, extraction of sensitive system files, and possible remote command execution on the system when deployed using the Explicit Proxy 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 · high confidence

The F5 SSL Intercept iApp versions 1.5.0 through 1.5.7 contains a vulnerability that can be exploited remotely without authentication when configured with the Explicit Proxy feature and SNAT Auto Map for egress traffic. The flaw allows attackers to modify system configuration, exfiltrate sensitive files, and potentially achieve remote command execution.

MitigationUpgrade the SSL Intercept iApp to version 1.5.8 or later, and review Explicit Proxy and SNAT Auto Map configurations to ensure they do not expose the vulnerable configuration patterns.

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

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
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/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. Verify SSL Intercept iApp is installed
    Run the following command on the F5 device to list installed iApp packages: tmsh list sys app service | grep -i ssl-intercept or check via GUI under iApps > Application Services
    Affected if The iApp is not present, then the system is not affected by this CVE.
  2. Determine the SSL Intercept iApp version
    Run: tmsh list sys app service <service_name> all-properties or check the version field in the iApp properties via the GUI under the SSL Intercept iApp package details
    Affected if The installed version falls within 1.5.0 through 1.5.7. Versions outside this range are not affected.
  3. Confirm Explicit Proxy is enabled
    Examine the SSL Intercept iApp configuration for the proxy type setting. Run: tmsh list sys app service <service_name> proxy-type or inspect the Explicit Proxy configuration via the GUI under the iApp properties.
    Affected if The proxy-type is set to explicit. If set to transparent or not explicitly configured, the system may not be vulnerable.
  4. Check if SNAT Auto Map is configured for egress
    Inspect the SSL Intercept iApp configuration for SNAT settings. Run: tmsh list sys app service <service_name> snat or review the egress traffic configuration via the GUI to determine if SNAT Auto Map is enabled.
    Affected if SNAT Auto Map is enabled for egress traffic. This configuration combined with Explicit Proxy creates the vulnerable state.

A system is affected only if SSL Intercept iApp version 1.5.0-1.5.7 is installed AND both Explicit Proxy and SNAT Auto Map are actively configured.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the SSL Intercept iApp to version 1.5.8 or later, and review Explicit Proxy and SNAT Auto Map configurations to ensure they do not expose the vulnerable configuration patterns.

Recommended fix Moderate confidence

SSL Intercept iApp version 1.5.8 or later

  1. 1. Access the F5 BIG-IP system via SSH or web management interface
  2. 2. Identify the current SSL Intercept iApp version by reviewing the deployed iApp template
  3. 3. Download the updated SSL Intercept iApp template from F5 Networks support portal (support.f5.com)
  4. 4. Upload the new iApp template to the BIG-IP system
  5. 5. Redeploy the SSL Intercept iApp using the updated template
  6. 6. Verify the deployment is functioning correctly with the Explicit Proxy and SNAT Auto Map settings
  7. 7. Test that configuration modifications and sensitive file access are no longer possible without authentication
Caveat Ensure compatibility of the new iApp version with the current BIG-IP TMOS version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ssl Intercept Iapp 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 help mitigating

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-0305 — 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-0305 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