CONTENTUM.COMA specialist. A plan. A result.

Vulnerabilities · 2022 · Splunk

CVE-2022-32155
Splunk vulnerability

In universal forwarder versions before 9.0, management services are available remotely by default. When not required, it introduces a potential exposure, but it is not a vulnerability. If exposed, we recommend each customer assess the potential severity specific to your environment. In 9.0, the universal forwarder now binds the management port to localhost preventing remote logins by default. If management services are not required in versions before 9.0, set disableDefaultPort = true in server.conf OR allowRemoteLogin = never in server.conf OR mgmtHostPort = localhost in web.conf. See Configure universal forwarder management security (https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation#Configure_universal_forwarder_management_security) for more information on disabling the remote management services.

Affected products

Splunk, Splunk Cloud Platform. The exact versions are in the references.

What to do now

  • Check your exposureFind out whether Splunk runs anywhere in your environment, including systems of suppliers.
  • UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
  • Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.

References

More vulnerabilities in Splunk products

Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.