dbcve.org
SplunkApplication

CVE-2017-17067

CRITICAL · 9.8 CVSS v3.0 Published 2017-11-30
Fix available
A fix is available. Upgrade to 6.3.12 / 6.4.9 or later.
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
Splunk Web in Splunk Enterprise 7.0.x before 7.0.0.1, 6.6.x before 6.6.3.2, 6.5.x before 6.5.6, 6.4.x before 6.4.9, and 6.3.x before 6.3.12, when the SAML authType is enabled, mishandles SAML, which allows remote attackers to bypass intended access restrictions or conduct impersonation attacks.

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

SAML authentication bypass vulnerability in Splunk Web where improper handling of SAML assertions when authType is enabled allows remote attackers to bypass authentication controls or impersonate legitimate users, achieving CRITICAL impact via network-exploitable unauthenticated attack vector.

MitigationApply vendor-supplied patches for affected versions (7.0.0.1+, 6.6.3.2+, 6.5.6+, 6.4.9+, 6.3.12+) and validate SAML authentication behavior post-patch; if patching is delayed, consider restricting SAML-enabled endpoints or implementing additional access controls.

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
SplunkApplication
Affected:>= 6.3.0, < 6.3.12>= 6.4.0, < 6.4.9>= 6.5.0, < 6.5.6>= 6.6.0, < 6.6.3.2>= 7.0.0, < 7.0.0.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
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. Identify installed Splunk version
    Run 'splunk version' from the Splunk installation directory or check the $SPLUNK_HOME/etc/splunk.version file
    Affected if The version falls within any of these ranges: 6.3.0 to 6.3.11, 6.4.0 to 6.4.8, 6.5.0 to 6.5.5, 6.6.0 to 6.6.3.1, or 7.0.0
  2. Confirm Splunk Web is enabled
    Check the web.conf configuration file in $SPLUNK_HOME/etc/system/local/ for enabled = 1 under [settings] stanza, or inspect the running Splunk process list for splunkweb
    Affected if Splunk Web interface is active and accessible on the configured port (default 8000)
  3. Verify SAML authentication is configured
    Examine the authentication.conf file in $SPLUNK_HOME/etc/system/local/ for authType = SAML in the [authentication] stanza, or check web.conf for authHandlerv2 = SAML
    Affected if SAML authentication is enabled with authType parameter configured
  4. Check for SAML IdP configuration
    Review the $SPLUNK_HOME/etc/system/local/ directory for saml.conf or look at the authentication.conf to identify the SAML identity provider settings
    Affected if SAML IdP is configured and mapped to Splunk users or groups

You are affected if your Splunk version is within the vulnerable ranges AND Splunk Web with SAML authentication (authType) is enabled and 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
Upgrade available Upgrade to 6.3.12 / 6.4.9 / 6.5.6 or later
Fixed in 6.3.126.4.96.5.6
Interim mitigation

Apply vendor-supplied patches for affected versions (7.0.0.1+, 6.6.3.2+, 6.5.6+, 6.4.9+, 6.3.12+) and validate SAML authentication behavior post-patch; if patching is delayed, consider restricting SAML-enabled endpoints or implementing additional access controls.

Recommended fix High confidence

Upgrade to 6.3.12 (if on 6.3.x), 6.4.9 (if on 6.4.x), 6.5.6 (if on 6.5.x), or 6.6.3.2 (if on 6.6.x). For long-term stability, consider upgrading to the latest 6.6.x or 7.0.x release which includes the fix.

  1. 1. Review Splunk upgrade documentation and ensure compatibility with your current environment and add-ons
  2. 2. Back up your Splunk configuration directory ($SPLUNK_HOME/etc/) and any custom apps
  3. 3. Download the appropriate fixed version for your current branch: 6.3.12 for 6.3.x, 6.4.9 for 6.4.x, 6.5.6 for 6.5.x, or 6.6.3.2 for 6.6.x
  4. 4. Stop the Splunk service using: $SPLUNK_HOME/bin/splunk stop
  5. 5. Install the upgrade package for your target fixed version
  6. 6. Start the Splunk service using: $SPLUNK_HOME/bin/splunk start
  7. 7. After upgrade, verify SAML authentication is working correctly by logging in via SAML
  8. 8. Confirm the Splunk Web version reflects the patched release: Settings > About > Version information
Caveat Review Splunk upgrade compatibility matrix as some custom apps or add-ons may require updates for newer Splunk versions; also test SAML configuration after upgrade before deploying to production.

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

Fix this in Splunk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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