CVE-2022-32155: Universal Forwarder management services allows remote login by default
First published: Wed Jun 15 2022(Updated: )
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.
Credit: prodsec@splunk.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Splunk Splunk | <9.0 | |
| Splunk Splunk Cloud Platform | <8.2.2106 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is CVE-2022-32155?
CVE-2022-32155 is a vulnerability in Splunk universal forwarder versions before 9.0 where management services are available remotely by default.
Is CVE-2022-32155 a vulnerability?
While CVE-2022-32155 introduces a potential exposure, it is not classified as a vulnerability.
What is the severity of CVE-2022-32155?
The severity of CVE-2022-32155 is high with a severity value of 7.5.
How does CVE-2022-32155 affect Splunk software?
CVE-2022-32155 affects Splunk universal forwarder versions before 9.0 and Splunk Cloud Platform versions before 8.2.2106.
How to mitigate CVE-2022-32155?
To mitigate CVE-2022-32155, each customer should assess the potential severity specific to their environment and consider enabling TLS cert hostname validation as recommended by Splunk.
- collector/nvd-index
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/author
- agent/weakness
- agent/last-modified-date
- agent/references
- agent/title
- agent/softwarecombine
- agent/description
- agent/first-publish-date
- agent/event
- agent/tags
- vendor/splunk
- canonical/splunk splunk
- canonical/splunk splunk cloud platform