CVE-2024-30078

  • SpinRite v6.1 Release #3
    Guest:
    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.
    /Steve.
  • 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!

    /Steve.
  • 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.)

Sushi

Miso hungry
Sep 26, 2020
29
7
Sushi Bar, USA
I’m sure Steve will go over this WiFi RCE CVE-2024-30078 in the next SN, but I wanted to confirm whether or not you must be authenticated to the same WiFi network as the attacker to have exposure. From what I can tell, both the target and attacker must be authenticated (not just associated) to the same WiFi network. Can anyone confirm this?
 
confirm whether or not you must be authenticated to the same WiFi network
According to Microsoft's report:

According to the CVSS metric, the attack vector is adjacent (AV:A). What does that mean for this vulnerability?

Exploiting this vulnerability requires an attacker to be within proximity of the target system to send and receive radio transmissions.


How could an attacker exploit the vulnerability?

An unauthenticated attacker could send a malicious networking packet to an adjacent system that is employing a Wi-Fi networking adapter, which could enable remote code execution.

So to me this means they just need to get to within radio range of your device. (So no access to the AP/SSID/WiFi is required.)
 
According to Microsoft's report:



So to me this means they just need to get to within radio range of your device. (So no access to the AP/SSID/WiFi is required.)
If that’s the case, this is a hair on fire situation. I appreciate your take and sincerely hope you are mistaken.
 
YUP! I was right, and you're right that it is a serious problem for people who have certain risk factors (they have nasty neighbours or they travel [unpatched] to places where nasty folk hang.) @Steve mentions it up top on this weeks show. https://www.grc.com/sn/sn-979-notes.pdf
Yeah this is pretty terrible. I hope MS finds it in their cold, black hearts to release patches for unsupported versions of Windows as well. I still have some Win 7 laptops I manage running 0patch. Hope 0patch guys are on top of it. Gonna have to figure that out next.