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.
References
Link | Resource |
---|---|
https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation#Configure_universal_forwarder_management_security | Mitigation Vendor Advisory |
https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates | Release Notes Vendor Advisory |
https://www.splunk.com/en_us/product-security/announcements/svd-2022-0605.html | Vendor Advisory |
Configurations
Configuration 1 (hide)
|
Information
Published : 2022-06-15 10:15
Updated : 2022-06-23 18:21
NVD link : CVE-2022-32155
Mitre link : CVE-2022-32155
JSON object : View
CWE
CWE-732
Incorrect Permission Assignment for Critical Resource
Products Affected
splunk
- splunk_cloud_platform
- splunk