Splunk Enterprise

Log4j vulnerable version found on Splunk 8.1.7.1

pbalbasdtt
Path Finder

Hi all,

During a scan of our infra, our system detected that in splunk version 8.1.7.1 , there is still present log4j library vulnerable to CVE-2021-44228. prior to the upgrade to this version we deleted the compromised files following the workaround in the Splunk Blog about this topic.

As this version has that vulnerability patched, I´d like to know how the process works, as there are log4j files in the affected version present. Thanks in advance for your help.

Best regards.

Labels (1)
Tags (2)
0 Karma

isoutamo
SplunkTrust
SplunkTrust

There have created 8.7.1.2 where those should be fixed. Also 8.1.8 is already out, I suppose that also this should contain those fixes.

0 Karma
Get Updates on the Splunk Community!

Automatic Discovery Part 1: What is Automatic Discovery in Splunk Observability Cloud ...

If you’ve ever deployed a new database cluster, spun up a caching layer, or added a load balancer, you know it ...

Real-Time Fraud Detection: How Splunk Dashboards Protect Financial Institutions

Financial fraud isn't slowing down. If anything, it's getting more sophisticated. Account takeovers, credit ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...