Spring4Shell - the next interpreter/RCE tsunami

  • SpinRite v6.1 Release #3
    The 3rd release of SpinRite v6.1 is published and may be obtained by all SpinRite v6.0 owners at the SpinRite v6.1 Pre-Release page. (SpinRite will shortly be officially updated to v6.1 so this page will be renamed.) The primary new feature, and the reason for this release, was the discovery of memory problems in some systems that were affecting SpinRite's operation. So SpinRite now incorporates a built-in test of the system's memory. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)


What could possibly go wrong?
Nov 7, 2020
Another month, another big CVE: https://www.tenable.com/blog/spring4shell-faq-spring-framework-remote-code-execution-vulnerability

Like the original Batman movie, you need several things (the Joker has toothpaste and shampoo as the poison combination I think....):
  • Java Development Kit (JDK) 9 or greater
  • Apache Tomcat as the Servlet container
  • Packaged as a WAR
  • spring-webmvc or spring-webflux dependency
I don't believe these to be the last Java libraries to have such flaws and am wondering how we begin to inventorise and assess these - because that's what the bad guys will be doing.

What do others think? Are we at the beginning of a trend?
It needs to be determined, but I don't think this will be as bad as the Log4J issue because I think one knows if one is running the Spring framework, and many business users have been conservative (i.e. slow to update) and so may be on older versions that are not affected. Never the less, there will likely still be confusion around "are we affected" and some heated activity around testing for vulnerability and the subsequent planning of updates.

EDIT: Just saw this: https://arstechnica.com/information...ll-the-internet-security-disaster-that-wasnt/

EDIT 2: There's also this https://isc.sans.edu/forums/diary/S...ate+Exploitation+Attempts+CVE202222965/28504/
Last edited: