CVE 2021 26701 - Microsoft, keeping it real for fourth of July weekend

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


New member
Jul 5, 2021
A few news outlets have been sort of chasing a somewhat cryptic warning issued from Microsoft on Thursday, right before the holiday weekend, titled: Update PowerShell versions 7.0 and 7.1 to protect against a vulnerability.

Microsoft writes:
If you manage yoiur Azure resources from PowerShell version 7.0 or 7.1, we’ve released new versions of PowerShell to address a .NET Core remote code execution vulnerability in versions 7.0 and 7.1.
We recommend that you install the updated versions as soon as possible.

Windows PowerShell 5.1 isn’t affected by this issue.

Also included is a link to showing limited details about the vulnerability.

I find this warning and the corresponding github page difficult to decode.
  • Is the risk limited to just Azure management via Powershell?
  • Are they recommending everyone update powershell across their server infrastructure? Or to update powershell on servers running applications that use the DOT NET framework?
Is this a sloppy warning, as indicating by spelling mistake "yoiur", that they tried to send out before heading out for a 4 day weekend? Should it just concern DOT devs or System Admins too?

Any one else following this? Any thoughts?