dbcve.org
SplunkApplication

CVE-2022-32157

HIGH · 7.5 CVSS v3.1 Published 2022-06-15
Fix available
A fix is available. Upgrade to 9.0 or later.
See remediation →
84/100
Remediation priority · High
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 Enterprise deployment servers in versions before 9.0 allow unauthenticated downloading of forwarder bundles. Remediation requires you to update the deployment server to version 9.0 and Configure authentication for deployment servers and clients (https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/ConfigDSDCAuthEnhancements#Configure_authentication_for_deployment_servers_and_clients). Once enabled, deployment servers can manage only Universal Forwarder versions 9.0 and higher. Though the vulnerability does not directly affect Universal Forwarders, remediation requires updating all Universal Forwarders that the deployment server manages to version 9.0 or higher prior to enabling the remediation.

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

Splunk Enterprise deployment servers before version 9.0 allow unauthenticated remote attackers to download forwarder bundles containing sensitive configuration data, credentials, and deployment settings. This occurs because the deployment server does not require authentication when serving bundle files to clients.

MitigationUpdate deployment servers to version 9.0, configure authentication between deployment servers and clients per Splunk documentation, and upgrade all managed Universal Forwarders to version 9.0 or higher before enabling authentication.

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:< 9.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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 Splunk Enterprise version
    Run 'splunk --version' from the Splunk bin directory, or check the About page in the Splunk web interface, or inspect the $SPLUNK_HOME/etc/splunk.version file
    Affected if Version is below 9.0 (e.g., 8.x, 8.0.x, 8.1.x, 8.2.x)
  2. Confirm deployment server is enabled
    Check the deployment server configuration: look for 'serverclass.conf' in $SPLUNK_HOME/etc/system/local/ or review the Deployment Monitor page in Splunk Web under Settings > Server Roles > Deployment Server
    Affected if Deployment server role is listed as active or serverclass.conf exists with configured server classes
  3. Verify deployment server listens on management port
    Check if port 8089 (default management port) is open and listening, or review outputs.conf for 'deployment' stanza in $SPLUNK_HOME/etc/system/local/
    Affected if Port 8089 is accessible and deployment server components are running
  4. Test unauthenticated bundle access
    Attempt to access http://<splunk_host>:8089/services/deployment/server/config?output_mode=json without authentication credentials
    Affected if Request returns HTTP 200 with deployment configuration data rather than redirecting to login

You are affected if Splunk Enterprise version is below 9.0 AND the deployment server feature is enabled and accessible without authentication.

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 9.0 or later
Fixed in 9.0
Interim mitigation

Update deployment servers to version 9.0, configure authentication between deployment servers and clients per Splunk documentation, and upgrade all managed Universal Forwarders to version 9.0 or higher before enabling authentication.

Recommended fix High confidence

Splunk Enterprise 9.0

  1. Update the Splunk Enterprise deployment server to version 9.0 or later
  2. Update all Universal Forwarders managed by the deployment server to version 9.0 or higher
  3. Configure authentication for deployment servers and clients by following the documentation at https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/ConfigDSDCAuthEnhancements#Configure_authentication_for_deployment_servers_and_clients
  4. Verify that authentication is properly enforced for forwarder bundle downloads
Caveat After enabling authentication, the deployment server can only manage Universal Forwarder versions 9.0 and higher; older forwarder versions will no longer be managed

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

Fix this in Splunk Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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