Hacker News
Java4Shell
rvwaveren
|next
[-]
https://hadrian.io/vulnerability-alerts/oracle-critical-secu...
seanieb
|previous
[-]
_msw_
|root
|parent
[-]
With log4shell, the exploit was a single shot where an attacker didn't even have to aim.
Just because you add "4shell" to the end of a brand name for a vulnerability, it doesn't make it the same.
What is the same, however, is the amount of fear and panic that come from very scary marketing landing pages. It leads to people thinking it's the same thing, and for those who lived through log4shell, a lot of stress that may not be necessary.
swingandamiss
|root
|parent
[-]
_msw_
|root
|parent
[-]
It's a bug that should be prioritized higher than many others, especially for internet-facing systems.
But it is common practice to describe the maximum possible negative effect of these bugs, and that may or may not manifest in a given software system. It will look rather bad in the abstract, and _potentially_ far less bad in practice in many cases.