Java4Shell, NGINX2Shell and more Why we are not at "Yellow"
Java4Shell, NGINX2Shell and more: Why we are not at “Yellow” 🚦
About a month ago, we went to Infocon Yellow for the first time in a few years. We decided to address the php2shell vulnerability and alert our readers to its significant impact. In the last few days, we had a major Microsoft 365 outage, a critical vulnerability in Java, and a critical vulnerability in NGINX, which was disclosed today. My plan today was to write a bit about attacks we are seeing against one of our Java-specific honeypots. But the results can be summarized in one sentence: We are seeing many attacks, but none that exploit Java4Shell (yet).
So why not go to “Yellow”? Often people ask why we are on “Green” if they are seeing hundreds or thousands of attacks hitting their system each day. My answer has been: “Green” means the Internet is broken as usual. As long as the status is “Green”, you should expect a normal “9-to-5” day. The reason behind our conservative Infocon is that you can’t be alert and “on guard” all the time. An alert status that is “high” all the time is meaningless and counterproductive.
You must not treat these recent vulnerabilities as “emergencies”. They are the “new normal”. Treat them as such. You will not be able to patch nginx2shell across a large organization before the exploit is released. Instead of trying to do the impossible and fail, think beyond the vulnerability of the day. A new reality requires new procedures and techniques.
Here are a few ideas:
- Automate patching as much as possible, in particular for less critical systems.
- Select less critical systems that would be at the end of your patch priority list.
- I’d rather take a system down myself than have ransomware do it for me.
- Having a system possibly patched is better than being sure the system isn’t patched.
- Additionally, reduce your exposure. Build a defensible architecture.
- Reduce the “blast radius” by restricting which data and resources each application can access.
- And reduce your supply chain exposure.
- Avoid chasing squirrels. Do not change your plan and drop what you are doing just because the world is going to end.
- Embrace AI tooling. It is immensely useful for automation. It is even more amazing at helping you get organized.