First published: Fri Mar 25 2022(Updated: )
The lack of validation of a key-value field in the Splunk-to-Splunk protocol results in a denial-of-service in Splunk Enterprise instances configured to index Universal Forwarder traffic. The vulnerability impacts Splunk Enterprise versions before 7.3.9, 8.0 versions before 8.0.9, and 8.1 versions before 8.1.3. It does not impact Universal Forwarders. When Splunk forwarding is secured using TLS or a Token, the attack requires compromising the certificate or token, or both. Implementation of either or both reduces the severity to Medium.
Credit: prodsec@splunk.com
Affected Software | Affected Version | How to fix |
---|---|---|
Splunk Splunk | <7.3.9 | |
Splunk Splunk | >=8.0<8.0.9 | |
Splunk Splunk | >=8.1<8.1.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2021-3422 has a medium severity rating due to its potential to cause a denial-of-service in affected Splunk Enterprise instances.
To fix CVE-2021-3422, upgrade your Splunk Enterprise instances to versions 7.3.9, 8.0.9, or 8.1.3 or later.
CVE-2021-3422 affects Splunk Enterprise versions prior to 7.3.9 and 8.0 versions before 8.0.9.
Yes, CVE-2021-3422 can be exploited remotely by sending specially crafted requests to the Splunk-to-Splunk protocol.
CVE-2021-3422 can lead to a denial-of-service condition, disrupting Splunk Enterprise operations when indexing Universal Forwarder traffic.