On Tuesday, the Apache project released an update for Geode. The update patches a typical deserialization issue we often see in Java software like Geode (CVE-2022-37021). Geode is a data management platform. It has to deal with a wide range of objects and formats. The simple allow listing approach usually doesn't work well in these environments.
But the vulnerability has a few dependencies:
And here comes Jolokia. "JMX on Capsaicin," as it calls itself. It provides a simple HTTP to JMX gateway. So it is somewhat interesting that I also saw some scans for Jolkia starting yesterday.
The scans all arrive from 188.8.131.52. I saw the first requests arrive at around 12:30 pm UTC on Aug 30th, a couple of hours before the vulnerability was made public on Geode's website. I am not sure if it was made public via other channels earlier.
The IP address itself is "unremarkable." It is assigned to ColoCrossing. We got some logs from this IP from 2015 and 2016. It looks like a "random colocated server" that gets compromised ever so often. Shodan only shows port 53 open.
The scans target ports 80 and 8080, likely targets for a Jolokia setup. Two URLs are requested:
All requests use a specific User-Agent:
My recommendation at this point:
The link between these scans and Geode is based on the timing of the scans. I do not have any actual exploit payloads right now. Time to figure out if it is worthwhile to set up a full Geode honeypot/VM.
Intrusion Detection In-Depth - SANS Cyber Safari 2022
Sep 1st 2022
Sep 1st 2022
3 weeks ago