If you still run the Java plug in for whatever reason, you might have notice as of late that when you install or update Java, it will check and offer to remove older versions of Java on your system. That’s a great idea as it ensures that you’re protected from threats that the older versions might have.
The problem is, it didn’t really work. Here’s what the FTC says on that front:
In its complaint, the FTC alleges that Oracle promised consumers that by installing its updates to Java SE both the updates and the consumer’s system would be “safe and secure” with the “latest… security updates.” During the update process, however, Oracle failed to inform consumers that the Java SE update automatically removed only the most recent prior version of the software, and did not remove any other earlier versions of Java SE that might be installed on their computer, and did not uninstall any versions released prior to Java SE version 6 update 10. As a result, after updating Java SE, consumers could still have additional older, insecure versions of the software on their computers that were vulnerable to being hacked.
What’s really bad about this is that Oracle knew about this as early as 2011.
#Fail
To make this go away, Here’s what Oracle has been ordered to do:
Under the terms of the proposed consent order, Oracle will be required to notify consumers during the Java SE update process if they have outdated versions of the software on their computer, notify them of the risk of having the older software, and give them the option to uninstall it. In addition, the company will be required to provide broad notice to consumers via social media and their website about the settlement and how consumers can remove older versions of the software.
The consent order also will prohibit the company from making any further deceptive statements to consumers about the privacy or security of its software and the ability to uninstall older versions of any software Oracle provides.
The FTC has published a blog post for consumers with more information about Java SE’s update issues.
My advice for a very long time has been not to run Java at all. Now would be a really good time to get rid of it. If you want to go ahead and make yourself a whole lot safer, visit http://java.com/uninstall where there are instructions on how to uninstall older versions of Java SE. This webpage also provides a link to the Java SE uninstall tool, which you can use to uninstall older versions of Java SE.
Oracle Patches Java Bug That’s Very Bad
Posted in Commentary with tags Java on April 21, 2022 by itnerdOracle has apparently patched a vulnerability in server-side Java that allowed an attacker to forge some kinds of SSL certificates and handshakes, along with several kinds of authentication messages. The vulnerabilities were discovered by ForgeRock security researcher Neil Madden and documented here. But here’s the info that what you need to know:
It’s hard to overstate the severity of this bug. If you are using ECDSA signatures for any of these security mechanisms, then an attacker can trivially and completely bypass them if your server is running any Java 15, 16, 17, or 18 version before the April 2022 Critical Patch Update (CPU). For context, almost all WebAuthn/FIDO devices in the real world (including Yubikeys*) use ECDSA signatures and many OIDC providers use ECDSA-signed JWTs.
If you have deployed Java 15, Java 16, Java 17, or Java 18 in production then you should stop what you are doing and immediately update to install the fixes in the April 2022 Critical Patch Update.
Lovely.
Kevin Bocek, VP, Security Strategy & Threat Intelligence at Venafi had this comment:
“This vulnerability is just one more example of how important machine identities are to global security. It allows an attacker to bypass the TLS session handshake for specific servers so they can install malware and look for ways to pivot across networks. This is a serious vulnerability that needs to be patched quickly.”
Given the severity of this bug, I’d be patching all the things right now before you get pwned now that this is out there.
Leave a comment »