lobsters score: 9 · tags: java, security
Earlier this year we found Squidbleed, an older cousin of Heartbleed, hiding in the Squid proxy since 1997. The bug was in Squid’s FTP module. But who uses FTP anymore? It’s a dead protocol and should be removed.
Isn’t Automated Clearing House (ACH) basically a bunch of glorified FTP servers? That’s pretty much anyone using direct deposit to get paid (so probably most salaries employees in the US, not sure about elsewhere).
I agree with the point that we should deprecate and remove old and unused features, or make them opt-in. But I suspect in a lot of cases that would affect more systems than this author realizes. The problem is vast.
score 2 · canonical
“RCE everywhere” is a bit of a stretch. Requires AVX-512, which if you squint a bit is anything Intel, and AMD Epyc but only Zen 4 and up (Genoa onward).
score 3 · canonical
But still, hardly everywhere. Java’s slogan of Build Once, Run Everywhere that this is alluding to is specifically that it doesn’t have such limitations.
score 2 · canonical
I have not checked what the big cloud hosters are running, but if e.g. AWS is actually running mostly those for x64, I think it’s the figure of speech as “AWS is everywhere”. If you hit 50% of companies, it’s everywhere enough ;)
score 1 · canonical
So if I read this right you need to
- use java + base64
- have request buffering off in your reverse proxy in front
- use AVX512 on the host
That’s an odd combination in my books
score 5 · canonical
Also looks like the only exploit is currently on G1. So won’t work if you’re using ZGC as far as I can tell.
score 1 · canonical
I’d hesitate to give that as a mitigation. Their RCE might not work as-is against ZGC, but the bug itself isn’t in G1 and at the very least can still be used for denial of service with ZGC.
score 1 · canonical
use AVX512 on the host
This was introduced with the intel Skylake family of processors in 2017. A big portion of servers is probably using newer CPUs than that.
score 1 · canonical
have request buffering off in your reverse proxy in front
From my reading, that’s just a prerequisite for their chosen approach to do the necessary Heap Feng Shui to achieve RCE. It is not said this is the only way to exploit the bug. It may be easier to crash a JVM or send it off into some weird unpredictable behaviour by corrupting random objects.
score 1 · canonical
What makes it odd? Java is a pretty popular language, base64 is a normal way to encode binary data as text, many CPUs have had AVX512 for a decade, you have to disable request buffering for a host of reasons. To me it seems like 3 fairly common orthogonal conditions, nothing odd about it?
score 1 · canonical
I don’t think this is that odd.
have request buffering off in your reverse proxy in front
From what I can tell, nginx is a bit of an outlier in having request buffering, and all of Traefik, Envoy (thus by extension many k8s gateway implementations), and HAProxy have it off by default. (I expect the mix of Traefik + Envoy will cover a lot of k8s setups.) The article also states that whether or not this affects it depends on the target in question: “Request buffering is not a general mitigation. Elasticsearch runs from one complete request, so this setting does not stop that chain.”
use AVX512 on the host
The article says “AMD EPYC and Ryzen: Zen 4 or newer”, and Zen 4 came out in 2022. As some arbitrary examples, Hetzner’s CPX VPSs seem to currently all be at least on Zen 4 Genoa, and Netcup seems to already have Zen 5 VPSs available (and G11 was already Zen 4).
use java + base64
Their initial testing describes pre-auth RCE on the default setups for Keycloak, Jira, Confluence, Artifactory, and Jenkins; and post-auth for Elasticsearch, Gerrit, and Kafka. I don’t think this is that rare, per se. At minimum, it probably affects a decent number of cloud infrastructure setups.
score 4 · canonical
I’m specifically thinking about typical VM setups that do not expose AVX512 in my experience.
Nginx though is widely used.
score 1 · canonical
This might depend on whether the hosting setups you’re familiar with look more like “nested VMs running on a single host with nginx in front” or “k8s cluster across 1 or more nodes” (in which case you don’t have the VM unless [unless using something like Kata] and nowadays are very very likely not using nginx).
score 2 · canonical
That’s fair - my experience is VMs + HA where you have to opt-in to newer CPU specs.
score 1 · canonical
It’s a bit unfortunate this claim inflation we’ve had on the security vulnerability side. The next time we have something of the same gravity as log4shell (which was in an entirely different league of bad) it’ll struggle a lot more to get visibility and traction given how often the alarm is being rung.
At the same time this sort of vulnerability isn’t nothing either. I don’t know what’s a good solution.
score 1 · canonical
Compared to log4shell this feels like a nothingburger from the guys who already took 2h of my time for a previous nothingburger.
Not even a mention of minecraft, the reason for lingering custom java installations running on big machines 24/7 - and which log4shell famously was an attack against.
score 2 · canonical
