We’re in for a hum-dinger of a Patch Tuesday today, with knowledgeable folks anticipating a big, scary new Windows exploit and a ‘Softie Captain Ameri
[See the full post at: January 2020 Patch Tuesday running commentary, from the skeptic’s corner]
|
Patch reliability is unclear. Unless you have an immediate, pressing need to install a specific patch, don't do it. |
-
January 2020 Patch Tuesday running commentary, from the skeptic’s corner
- This topic has 167 replies, 50 voices, and was last updated 3 years, 10 months ago.
AuthorViewing 64 reply threadsAuthor-
-
They usually drop sometime around 1:00 PM EST.
1 user thanked author for this post.
-
Did anyone received the early notification for this month updates? Normally we received an advance notification about a week before from Microsoft Premier.
1 user thanked author for this post.
From some of the articles running on Forbes there appears to be some scare tactics at play even regarding 7 and some wav sound file crypto reporting as well as the fact that Windows 7 is getting one last round of updates for Jan 14(today) before it’s all over.
Now for Windows 7 patches in Feb 2020 that’s when it’s really not getting any new security patches(For Consumers at least). I’m beginning to suspect that MS is embarrassed by missing that 1 Billion devices number goal that’s still to this day at around 900 million for 10. So those scare tactics is why there needs to be DEFCON3 or higher before I’ll even think about it.
That Sky Is Falling theme is definitely in play today at 7’s EOL but that’s still not going to help any 1 Billion devices goal from being met on 10. People are just not limited to only PCs/Laptops for any light computing needs so Phones/Tablets for video/browsing and other light computer needs sees more devices running Android and iOS filling that need.
-
Yep. That’s why I’m going to dodge the “Win7 is dead” noise today and add to Susan’s level-headed FAQ tomorrow.
Assuming we’re all still here. 🙂
9 users thanked author for this post.
-
Microsoft releases Patch Tuesday updates at 10:00am PST US. It is only 9:00am in Redmond at this time.
4 users thanked author for this post.
-
-
-
-
Perhaps this apples-to-oranges comparison of Microsoft and Ford would be more appropriate if Ford refused to allow anyone to drive their cars unless they agree to an EULA that absolves Ford of any damage caused by the use of their product.
1 user thanked author for this post.
-
-
Until patch release and until analysis, I treat the prophecies of doom with exactly what they’re due.
We are SysAdmins.
We walk in the wiring closets no others will enter.
We stand on the bridge, and no malware may pass.
We engage in support, we do not retreat.
We live for the LAN.
We die for the LAN.4 users thanked author for this post.
After reading the article, I got the “boy who cried wolf” impression. Woody, it seems like you’re starting to become pacified to all the threats. Just because nothing has materialized with recent threats, doesn’t mean something won’t with each new one. I definitely agree we should wait to see if any bugs are introduced, but don’t start making us believe there’s no urgency until proven that there really is no urgency.
1 user thanked author for this post.
-
Well, OK, but I’d put the shoe on the other foot.
Don’t patch until there’s a lot of evidence that you need to patch.
It’s a half-full/half-empty sort of thing. But given MS’s horrible track record with botched patches, I’d say the burden of proof is on MS.
Total of 23 users thanked author for this post. Here are last 20 listed.
-
For me, the evidence that there is a need to patch is the fact that a patch has been made available. I much prefer being the one who says, “Patches installed, no issues, no problems, no BSOD’s, no black screens” than the one who says, “Help! The hackers got my PC!”
As for “given MS’s horrible track record with botched patches, I’d say the burden of proof is on MS.” I’ve had no botched patches, and I have installed every patch that has been offered to my systems from Windows 7 all the way through Windows Version 1909 (OS Build 18.363.592).
In the event that I should one day become botched by a patch, I’m six minutes away from being un-botched.
Always create a fresh drive image before making system changes/Windows updates; you may need to start over!We were all once "Average Users". We all have our own reasons for doing the things that we do with our systems, we don't need anyone's approval, and we don't all have to do the same things. -
-
The PC is a dual boot with 6 drives, 4 of which are SSD’s (three 250GB, one 1TB), two are 1TB SSHD’s. The OS partition is 100GB, the image file is 38.3GB located on the 1TB SSD.
However, don’t be deceived by the “SSD’s”. I had similar performance (~six minute restoration) when I had four spinners in the box. The partition size is the primary contributor to the speed boost. I’ve been doing this for years and years.
Task Scheduler runs Image For Windows scripts for my OS partition, my Program Files partition and my Users partition (they’re all 100GB partitions) in the wee hours every Sunday morning while I sleep. Task Scheduler also runs a Robocopy batch file twice daily to copy my Documents folder to my OneDrive folder. There it’s synced through the cloud to my NAS OneDrive folder. That way, any data in between drive images is already saved in three separate locations.
I do the same for the B side of my dual boot.
Always create a fresh drive image before making system changes/Windows updates; you may need to start over!We were all once "Average Users". We all have our own reasons for doing the things that we do with our systems, we don't need anyone's approval, and we don't all have to do the same things.-
This reply was modified 3 years, 10 months ago by
.
-
This reply was modified 3 years, 10 months ago by
2 users thanked author for this post.
-
This reply was modified 3 years, 10 months ago by
-
-
-
I, too, go by my own anecdotal evidence.
Group B for WIN7 w/ ESU, plus trying out Linux builds in dual boot.
2 users thanked author for this post.
-
Anecdotal evidence is valuable and most welcome!
1 user thanked author for this post.
-
-
-
I have not installed the Windows 7 December 2019 Monthly Quality and Security Rollup yet for that reason. Somehow I can’t bring myself to do it knowing that I have to cancel the nag screen. Curious to see what happens on 1/15/20.
My Win 10 is totally patched.
Win 10 Home 22H2
-
I installed the rollup on both my machines over the weekend and have yet to see a nag screen on either of them.
1 user thanked author for this post.
-
I’ve got both of the EOSNotify and EOSNotify2 tasks disabled in Task Scheduler. It was not a big deal for me to disable them. EOSNotify2 has its start date shown as Jan. 15, 2020 at 12:00 pm. If by chance I do still see a Nag screen, I’ll go back and delete the tasks altogether, and maybe even move the EOSNotify.exe program in System32 to the Recycle Bin.
Have you seen the price of Tums? It's enough to give you heartburn. -
Did the same, went right to the task scheduler and disabled the TWO EOS Notify tasks after the installation of the December KB 4530734 ROLLUP. Found them under SETUP in the TASK SCHEDULER and also checked the active tasks and EOS NOTIFY is no longer in the active tasks. Tomorrow evening will sign on to see if the task is really gone. From what I can see it appears so! Let us know and thanks!
Win 10 Home 22H2
1 user thanked author for this post.
-
The January patches are now listed in the Microsoft Update Catalog:
https://www.catalog.update.microsoft.com/Search.aspx?q=2020-01
1 user thanked author for this post.
I should really have put a bet on at the local bookmakers, predicting that there would be a doomsday threat on EOL day for Windows 7 – it was totally predictable, whether real or imagined. Yes we have to take such things seriously, but that doesn’t mean we have to panic.
2 users thanked author for this post.
Group B Security-only Updates and the IE11 Cumulative Update have been updated for January 2020 on AKB2000003.
There is a new SSU for Win7. KB4536952 32-bit ot 64-bit
The documentation for the SSU DOES NOT mention the ESU or say it is just for the ESU.-
-
-
When did they ever list the real changes? 🙂
BTW, both Monthly Rollup KB4534310 and Security Only KB4534314 contain updated WUA client, which they didn’t mention in the articles
on another hand, ESU licenses are updated to officially support these editions:
Enterprise,EnterpriseE,EnterpriseN,Professional,ProfessionalE,ProfessionalN,Ultimate,UltimateE,UltimateN1 user thanked author for this post.
-
-
-
-
Purely speculation here, but MS did release some unplanned emergency patches for major threats for Windows XP after EOL. Maybe this SSU is intended to prepare for any such emergency patches for Windows 7.
i7-10700k - ASROCK Z590 Pro4 - 1TB 970 EVO Plus M.2 - DDR4 3200 x 32GB - GeForce RTX 3060 Ti FTW - Windows 10 Pro
-
SSUs never cover or fix security vulnerabilities
1 user thanked author for this post.
-
-
SSUs are updates for the Windows Update mechanism itself.
3 users thanked author for this post.
-
-
Not the case.
1 user thanked author for this post.
-
I’m aware, I just mean, perhaps the purpose of the SSU is to make certain that the machine will be able to receive and install any future emergency patches which might be issued.
i7-10700k - ASROCK Z590 Pro4 - 1TB 970 EVO Plus M.2 - DDR4 3200 x 32GB - GeForce RTX 3060 Ti FTW - Windows 10 Pro
1 user thanked author for this post.
-
-
From Google:
Secure Hash Algorithms, also known as SHA, are a family of cryptographic functions designed to keep data secured. It works by transforming the data using a hash function: an algorithm that consists of bitwise operations, modular additions, and compression functions.
I must have misunderstood.
Have you seen the price of Tums? It's enough to give you heartburn.1 user thanked author for this post.
-
You didn’t completely misunderstand.
A recent SSU enabled the application of updates signed only with SHA-2; this update was made necessary by the cracking of SHA-1 and by Microsoft moving to SHA-2-only code signing.
So… to make a short story long, you had to apply the SSU to enable the more-securely-signed updates to make your system more secure.
🙂
1 user thanked author for this post.
-
-
-
Seeker/cannon fodder report:
KB4532938 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10 Version 1909 for x64
KB4528760 Cumulative Update for Windows 10 Version 1909 for x64-based Systems
KB890830 Windows Malicious Software Removal Tool x64Restart required/accomplished. So far, so good.
Always create a fresh drive image before making system changes/Windows updates; you may need to start over!We were all once "Average Users". We all have our own reasons for doing the things that we do with our systems, we don't need anyone's approval, and we don't all have to do the same things.-
-
KB4532938 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10 Version 1909 for x64
KB4528760 Cumulative Update for Windows 10 Version 1909 for x64-based Systems
KB890830 Windows Malicious Software Removal Tool x64Same updates for me as well. Hiding for now.
Win10 Pro
We’re in for a hum-dinger of a Patch Tuesday today, with knowledgeable folks anticipating a big, scary new Windows exploit and a ‘Softie Captain Ameri
[See the full post at: January 2020 Patch Tuesday running commentary, from the skeptic’s corner]Martin Brinkmann has the full breakdown :
Reminder for Windows 7 users, the full screen notificaton starts tomorrow, from:
https://support.microsoft.com/en-us/help/4534310
January 14, 2020—KB4534310 (Monthly Rollup)
IMPORTANT Starting on January 15, 2020, a full-screen notification will appear that describes the risk of continuing to use Windows 7 Service Pack 1 after it reaches end of support on January 14, 2020. The notification will remain on the screen until you interact with it. This notification will only appear on the following editions of Windows 7 Service Pack 1:
Two WiFi engineers got married. The reception was fantastic.5 users thanked author for this post.
-
A7,
Those updates are available to Win8.1 and you have to click on “Install” to download and install them.
Just close the window and wait for AskWoody to give the all-clear.1 user thanked author for this post.
According to MS, the big, scary vulnerability only affects Windows 10 and Server, not W7 / 8
https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-0601
Yay, Windows 10 , most secure Windows ever 😉
Windows 10 Home 22H2, Acer Aspire TC-1660 desktop + LibreOffice, non-techie
7 users thanked author for this post.
-
-
I haven’t updated yet cause the updates won’t be available to me till tomorrow morning but I did find the EOSNotify and EOSNotify2 in task scheduler and I disabled both of them. Hope I didn’t kill my computer.
I just went back in to task scheduler to look at them again and they have disappeared from the lineup. oh oh
Edition Windows 11 Pro
Version 23H2
Installed on 10/19/2022
OS build 22631.27151 user thanked author for this post.
-
There is nothing in gHacks about this vulnerability, at this time. (3:13 PM, EST) Only two garden variety CVEs, one about a remote desktop attack and one about an exploit that makes IE11 vulnerable to a phishing attack, where the user is bamboozled, as usual, to click something that should not be clicked.
However, the story so far, as I can ascertain it, is thus: at NSA they found this vulnerability and then alerted MS about it. Ms, on receiving the notice from the super-spooks, took quick action, and here we are.
As evidence for this story, there is this document, directly from Spook Central:
https://media.defense.gov/2020/Jan/14/2002234275/-1/-1/0/CSA-WINDOWS-10-CRYPT-LIB-20190114.PDF
Notice that, in the first two paragraphs it says that this CVE affects (only?) Windows 10 and Server 216/219:
“NSA has discovered a critical vulnerability (CVE-2020-0601) affecting Microsoft Windows cryptographic functionality. The certificate validation vulnerability allows an attacker to undermine how Windows verifies cryptographic trust and can enable remote code execution. The vulnerability affects Windows 10 and Windows Server 2016/2019 as well as applications that rely on Windows for trust functionality. Exploitation of the vulnerability allows attackers to defeat trusted network connections and deliver executable ode while appearing as legitimately trusted entities. Examples where validation of trust may be impacted include:
HTTPS connections
Signed files and emails
Signed executable code launched as user-mode processes
The vulnerability places Windows endpoints at risk to a broad range of exploitation vectors.
NSA assesses the vulnerability to be severe and that sophisticated cyber actors will understand the underlying flaw very quickly and, if exploited, would render the previously mentioned platforms as fundamentally vulnerable.”As to scaremongering and the Boy That Cried Wolf (too many times):
The boy cried “Wolf” around his village, a place and a time when wolves were a real problem, because they used to come in big packs and kill and eat its inhabitants. So crying “wolf” was serious business that got the boy a lot of attention. He liked that, and so he kept crying “wolf” with no real wolves in sight. After he did it three times, people decided to ignore him and stop wasting time following the alarms from a proven purveyor of fake alarms.
Until, one day, the wolves really came, they killed and ate everybody in the village, except for the boy and his family. Because Dad had kept, “just in case the boy was not lying, for a change”, his trusty MP-15 well greased, cleaned and loaded, set for “burst” firing (those were the days!) and always close at hand.
Moral of this story: Don’t worry about sudden, alarming news of fierce bugs out there to get people (even if the news come from people close to you, or usually trusted — not the same thing, obviously) but keep the patches handy. Don’t rush to install them, though, but wait — as usual — for indications that they are themselves bug-free, then install them.
And this being my last Patch Tuesday ever (as Win 7 is my last and only Windows for evermore), all I can say is: Wow! What a way to go!
Ex-Windows user (Win. 98, XP, 7); since mid-2017 using also macOS. Presently on Monterey 12.15 & sometimes running also Linux (Mint).
MacBook Pro circa mid-2015, 15" display, with 16GB 1600 GHz DDR3 RAM, 1 TB SSD, a Haswell architecture Intel CPU with 4 Cores and 8 Threads model i7-4870HQ @ 2.50GHz.
Intel Iris Pro GPU with Built-in Bus, VRAM 1.5 GB, Display 2880 x 1800 Retina, 24-Bit color.
macOS Monterey; browsers: Waterfox "Current", Vivaldi and (now and then) Chrome; security apps. Intego AV3 users thanked author for this post.
-
So now you know.
Ex-Windows user (Win. 98, XP, 7); since mid-2017 using also macOS. Presently on Monterey 12.15 & sometimes running also Linux (Mint).
MacBook Pro circa mid-2015, 15" display, with 16GB 1600 GHz DDR3 RAM, 1 TB SSD, a Haswell architecture Intel CPU with 4 Cores and 8 Threads model i7-4870HQ @ 2.50GHz.
Intel Iris Pro GPU with Built-in Bus, VRAM 1.5 GB, Display 2880 x 1800 Retina, 24-Bit color.
macOS Monterey; browsers: Waterfox "Current", Vivaldi and (now and then) Chrome; security apps. Intego AV1 user thanked author for this post.
-
This vulnerability exists in Windows 7, too. It probably has been there since Windows 2000.
https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-0601
Thus far, Win 7 is not on the list.
Group B for WIN7 w/ ESU, plus trying out Linux builds in dual boot.
-
Shoot, you’re right. I was getting my lists crossed with the one security vulnerability actually marked as “critical” this month, which is the RDP vulnerability.
Someone’s going to need to explain to me why the certificate spoofing vulnerability has an “important” rating, not critical.
4 users thanked author for this post.
>>edited for clarity<<
The same updates were pushed to my Dell Latitude E5420. That is to say more specifically, when I logged in and went to All settings > Update & Security the announcement that there are updates available for download was at the top of the page, followed by the list of available downloads, and below that the prominent “Download” button. I had to click the button to initiate the download and update process. No issues with my laptop.
>>end of edit<<
The same updates are being restarted/installed on my NAS as I type this.
All is well. I haven’t updated the B side of my laptop yet, but I’ll get around to that one soon enough. Four out of five installations updated with no issues.
Always create a fresh drive image before making system changes/Windows updates; you may need to start over!We were all once "Average Users". We all have our own reasons for doing the things that we do with our systems, we don't need anyone's approval, and we don't all have to do the same things.Write-up by the SANS Internet Storm Center about Patch Tuesday, especially CVE-2020-0601:
Microsoft Patch Tuesday for January 2020Their summary chart shows that Microsoft only rates CVE-2020-0601 as Important, not Critical.
1 user thanked author for this post.
-
Hello WB,
For those who are running the Java SE Runtime Environment (as am I, due to the requirement of one of my banks), then the JRE has been updated to version 8u241 (digitally signed on 2019.12.11):
https://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html
Cheers,
AJN
2 users thanked author for this post.
-
KB4503548 Microsoft NET Framework 4.8 for Windows 7 for x 64 is the INSTALLER for .NET 4.8. We have not been recommending it for Win7. I would suggest leaving it hidden.
If December 2019 .NET Security and Quality Rollup is CHECKED, I would recommend installing it after you unhide it. If it is UNCHECKED, do not check it and it won’t get installed, But you should rehide it so you get the SSU KB4536952. All the checked updates in the queue can be installed at once, providing they have the DEFCON approval.
3 users thanked author for this post.
-
-
-
The Rollup is a bundle of independent patches for each separate version of .NET. If you do not have the version of .NET installed, the patch for that version is not applied. The Rollup installation manages patching only the individual version(s) you have installed.
1 user thanked author for this post.
-
-
Hey Y’all,
Here’s what I got today on my Test machine (Seeker)!
I’ll keep Y’all posted if any problems arise. 😎-
Hey Y’all,
Now 3 days in on my Test machine w/o issue. I’ve also decided to install on my main desktop and am 2 days in with that and also no problemo! HTH 😎
1 user thanked author for this post.
-
Hey Y’all,
I said I’d keep you updated so here it is. Over the last two days I’ve noticed that my machine will no longer wake from sleep. This used to take a light tap on the power button but this now restarts the machine!
So I decided to restore my C: partition from my Macrium Reflect backup on my H: drive (3rd physical drive {SSD} in the machine. Guess what the Reflect rescue media only recognizes the firs 2 drives C: & G:, although when booted into Windows it sees them. The really funny part is it sees them for purposes of backup but not restore and it happens in V6 & V7.
Well back to the topic, I copied the backup file to the G: drive and restored it successfully and the machine once again behaves like it used to. So there is something in the cumulative updates causing the problem.
In the process of trouble shooting this problem I also noticed that options for turning off Fast Start are no longer in the Power Options menus in 1909.
HTH 😎
1 user thanked author for this post.
-
-
Czech goverment… Czech government just does not have a clue what is going on. Honestly I checked our National Center of Cyber Security web and the last update is dated to 9.12.2019 🙂 No politics here, but you get my point.
NCKBDell Latitude 3420, Intel Core i7 @ 2.8 GHz, 16GB RAM, W10 22H2 Enterprise
HAL3000, AMD Athlon 200GE @ 3,4 GHz, 8GB RAM, Fedora 29
PRUSA i3 MK3S+
1 user thanked author for this post.
So, here we are, the last regular Patch Tuesday for Windows 7.
I’m not gonna lie – this is enjoyably interesting. :]
Group B for WIN7 w/ ESU, plus trying out Linux builds in dual boot.
1 user thanked author for this post.
-
I’m going to venture a guess.
The SSU is not in the list of patches to be installed, but it downloads and installs with the CU. I believe it presents itself in the Update History as the update as well as the CU doing this. If you look in the Installed Updates, you will see it listed as two separate updates with two different KB numbers.Supposedly, the update mechanism installs the SSU first, then the CU. This may be what you are seeing with what appears to be a second install. The Build number doesn’t change until the installation completes after the second reboot.
2 users thanked author for this post.
-
Another 1909 WU without issues (Jan CU, MSRT, Net Frmwk 4.8, Svc Stack). Images were ready. 18363.592
Are you encountering the File Explorer Search bug?
No, although with an SSD/HDD combo an SSD article led me to Turn OFF Search Indexing, IF THAT matters / Cortana Never Active …. Just did a test search & all remains well.
W10 Pro 22H2 / Hm-Stdnt Ofce '16 C2R / HP Envy Desk-Ethernet - SSD-HDD/ i5(8th Gen) 12GB / GP=2 + FtrU=Semi-Annual + Feature Defer = 1 + QU=0
Updates that came in this morning:
Security and Quality Rollup for .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows 7 SP1 and Windows Server 2008 R2 SP1 (KB4535102)
2020-01 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4534310)
Windows Malicious Software Removal Tool x64 – January 2020 (KB890830)
All Checked and hiddenServicing stack update for Windows 7 SP1 and Server 2008 R2 SP1 (KB 4536952)
Unchecked and hiddenChecked for updates again
Microsoft .NET Framework 4.8 for Windows 7 forx64 (KB4503548)
Unchecked and hiddenEdition Windows 11 Pro
Version 23H2
Installed on 10/19/2022
OS build 22631.27151 user thanked author for this post.
-
-
The .NET Rollups should be installed if they are CHECKED.
Microsoft .NET Framework 4.8 for Windows 7 KB4503548 is the .NET 4.8 Installer.
If you have the earlier version of .NET 4.8 installed, AND KB4503548 is checked, you should install it.
If you don’t already have .NET 4.8 installed, it is not recommended for Win7. You shoud keep it hidden.
-
EOSnotify tasks were disabled on Sunday.
My PC has been running since 5 AM this morning with no sign of the nag screen.
1 user thanked author for this post.
More from the SANS Internet Storm Center:
One quote:
Which operating systems are affected?
Only Windows 10 and Windows Server 2016 and 2019 are affected. Windows 7 is not affected. There was some confusion about this because Windows 7 is no longer officially supported after this patch release. But the January 14th patch Tuesday did cover Windows 7. The affected library, crypt32.dll (CryptoAPI), is present in older versions of Windows, including Windows 7. But not all versions of this library are affected. Out of support versions of Windows 10, like Windows 10 1709, are likely vulnerable, and you should upgrade to Windows 10 1809, the current “long term support” version.
The video referenced in the article can be viewed on YouTube:
SPECIAL WEBCAST: What you need to know about the Crypt32.dll / CryptoAPI Flaw-
A slide from their PowerPoint presentation on CVE-2020-0601:
More from the SANS Internet Storm Center:
CVE-2020-0601 Followup
One quote:
Which operating systems are affected?
Only Windows 10 and Windows Server 2016 and 2019 are affected. Windows 7 is not affected. There was some confusion about this because Windows 7 is no longer officially supported after this patch release. But the January 14th patch Tuesday did cover Windows 7. The affected library, crypt32.dll (CryptoAPI), is present in older versions of Windows, including Windows 7. But not all versions of this library are affected. Out of support versions of Windows 10, like Windows 10 1709, are likely vulnerable, and you should upgrade to Windows 10 1809, the current “long term support” version.
The video referenced in the article can be viewed on YouTube:
SPECIAL WEBCAST: What you need to know about the Crypt32.dll / CryptoAPI FlawSANS has updated CVE-2020-0601 Followup including the statement: UPDATE: An Exploit has been made public!
I’m not going to apply updates yet, but I’m definitely going to continue monitoring information from SANS and others.
A new article from Ars Technica:
Critical Windows 10 vulnerability used to Rickroll the NSA and GithubFirst two paragraphs:
Less than a day after Microsoft disclosed one of the most critical Windows vulnerabilities ever, a security researcher has demonstrated how attackers can exploit it to cryptographically impersonate any website or server on the Internet.
Researcher Saleem Rashid on Wednesday tweeted images of the video “Never Gonna Give You Up,” by 1980s heartthrob Rick Astley, playing on Github.com and NSA.gov. The digital sleight of hand is known as Rickrolling and is often used as a humorous and benign way to demonstrate serious security flaws. In this case, Rashid’s exploit causes both the Edge and Chrome browsers to spoof the HTTPS verified websites of Github and the National Security Agency. Brave and other Chrome derivatives, as well as Internet Explorer, are also likely to fall to the same trick. (There’s no indication Firefox is affected.)
-
-
-
Note that while some of the articles that I link to are meant for security professionals (e.g. SANS), some of them are meant for the general public (e.g. Ars Technica) on websites that may or may not be primarily focused on cybersecurity (Ars Technica is not).
1 user thanked author for this post.
-
-
Windows 7 January patches: KB4535102 .NET
KB4534310 Win 7I had not installed them Tuesday (I only installed MRT). This morning I powered down to install a new SSD disk on which I will install Win 10. But Windows Update had these two checked, so they auto-installed prior to the power down. Then I rebooted in safe mode to check to see if the SSD was OK, and Windows did its normal “chkdsk c:” and other things (because it took more than 12 minutes). But in safe mode Windows does not tell me what it is doing, as it displays the driver names that it has loaded before safe mode starts. Then I rebooted into regular mode. I checked the EventVwr, and it showed that the two patches had been installed, and a reboot was required. Then I saw that the two patches had failed with code 80070643. Widows update now shows me only KB4536952 2020-01 Servicing Stack Update Win 7. I have no idea what that 80070643 error code means. I looked at one thread (via Google), and it was obvious that all the “those knowledgeable” who were responding had no idea what the error code signified. Would I get that error code if my reboot after the patch installation was not a reboot into full Windows 7? Many years ago I would patch Win 7, then reboot into XP to patch, and then reboot into Win 7; back then the Win 7 patches would not complete installation because I had rebooted into XP.
I know that I will not see the two failed patches again (if indeed they did not install) until I install the SSU update. Is the SSU update safe, or is it too soon to know if the SSU patch is OK to install?
1 user thanked author for this post.
-
the Servicing Stack is safe to install.
But, we are still on DEFCON-21 user thanked author for this post.
-
Here is what I received for Windows 7 2020-01 on 1/14/2020
Security and Quality Rollup for .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows 7 SP1 and Windows Server 2008 R2 SP1 (KB4535102) – are there issues with this Rollup? This is labeled as Recommended and not Important.
2020-01 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4534310)
Windows Malicious Software Removal Tool x64 – January 2020 (KB890830)
All HiddenMicrosoft .NET Framework 4.8 for Windows 7 forx64 (KB4503548)
Hidden and do not plan to install on Windows 7.Windows update automatically checked again and the following appeared:
Servicing stack update for Windows 7 SP1 and Server 2008 R2 SP1 (KB 4536952)
HiddenThis leads me to the question of last month. The SSU appeared AFTER all the updates were HIDDEN, therefore, when the all clear is given, will the updates install first or the SSU?
NOTE: KB 45330905 .NET Security and Quality Rollup for December 2019 was not installed as yet as some have reported issues with the .NET rollup. When I do install, it will be before the other January Patches. Has anyone had issues with the .NET Security Rollups? Also, if I skip this December rollup will I be OK with just the final January Rollup? This is labeled as Recommended and not Important.
Thanks….
Win 10 Home 22H2
-
Just let Windows Update install the CHECKED Jan updates however it does it (like last month).
But we are still on DEFCON-2 so WAIT until we know if there are any problems.1 user thanked author for this post.
-
-
Rule of thumb:
If it’s CHECKED by default install it.
If it’s UNCHECKED by default, do not install it. MS has left it unchecked for a reason.1 user thanked author for this post.
-
-
-
New article from the SANS Internet Storm Center:
Summing up CVE-2020-0601, or the Let?s Decrypt vulnerabilityOf special interest, you can go to https://curveballtest.com/ to test if your browser is vulnerable to CVE-2020-0601.
On my unpatched system, Firefox (my default browser) is not vulnerable and Microsoft Edge is vulnerable.
3 users thanked author for this post.
New article from the SANS Internet Storm Center:
Summing up CVE-2020-0601, or the Let?s Decrypt vulnerabilityOf special interest, you can go to https://curveballtest.com/ to test if your browser is vulnerable to CVE-2020-0601.
On my unpatched system, Firefox (my default browser) is not vulnerable and Microsoft Edge is vulnerable.
I am using Firefox 72.0.1
(https://curveballtest.com/ tells me in big letters I am vulnerable. In smaller letters it says Firefox is NOT vulnerable. So…yea or nay, yin or yang? Any ideas?
Thank you.
DriftyDonN
Win10 ver 1903 build 18362.535, paused updates til 17Feb
-
-
You’re vulnerable because you’re running Win 10.
I don’t think that statement is true. I have Windows10 Home 1909.
I have not updated yet. Using FF 69.0.3 browser.
My results:
-
-
-
In about:config, double-click a line to change the value.
If it’s a true/false value, double-clicking the line will toggle it.
If it’s some other kind of value, double-clicking the line will open up the value so that it can be changed.
If a line is bolded, the value has been changed. If not, it is the default. Changing a value back to the default will remove the bolding.
1 user thanked author for this post.
In about:config, double-click a line to change the value.
If it’s a true/false value, double-clicking the line will toggle it.
If it’s some other kind of value, double-clicking the line will open up the value so that it can be changed.
If a line is bolded, the value has been changed. If not, it is the default. Changing a value back to the default will remove the bolding.
security.<wbr />enterprise_roots.<wbr />enabled
This line has a padlock at the beginning(before “security…”) and the line is greyed out. The other lines are not. The value is set at “true” now…it was false.
Thanks for helping!
D
BTW, no response to double clicking, no real choice with right click(normal drop down menu)
-
I’m sorry, but I’ve never seen that and have no idea what would cause it. The only way that I can think of to fix it is to find the profile directory with the configurations, find the correct file, and manually edit it with a text editor.
1 user thanked author for this post.
Viewing 64 reply threads
Plus Membership
Donations from Plus members keep this site going. You can identify the people who support AskWoody by the Plus badge on their avatars.
AskWoody Plus members not only get access to all of the contents of this site -- including Susan Bradley's frequently updated Patch Watch listing -- they also receive weekly AskWoody Plus Newsletters (formerly Windows Secrets Newsletter) and AskWoody Plus Alerts, emails when there are important breaking developments.
Get Plus!
Recent Topics
-
Top Hookup Platform (Awaiting moderation)
by 31 minutes ago
-
Debian SparkyLinux 7.2 “Orion Belt”
by 3 hours, 39 minutes ago
-
Burt Wolf on Communication
by 5 hours, 54 minutes ago
-
Converting HHD iMac to SSD
by 31 minutes ago
-
Bluetooth hack : Hi, My Name Is Keyboard
by 1 hour, 25 minutes ago
-
Windows sees RAW, chkdsk sees NTFS
by 4 hours ago
-
Microsoft SMB V1 removal – any updated information
by 3 hours, 48 minutes ago
-
ISO portable PC keyboard that matches standard Dell keyboard
by 16 hours, 47 minutes ago
-
End of support W10
by 22 hours, 42 minutes ago
-
MS-DEFCON 2: Copilot for Christmas
by 6 hours, 33 minutes ago
-
Sudden appearance of Edge Search Bar
by 13 hours, 28 minutes ago
-
LogoFAIL firmware exploit bypasses hardware and software security
by 13 hours, 8 minutes ago
-
Microsoft outlook ignores the registry keys
by 1 day, 23 hours ago
-
Windows 11 Insider Preview Build 22635.2841 released to BETA
by 1 day, 18 hours ago
-
Thunderbird doesn’t open folders at most recent email in Inbox
by 22 hours, 45 minutes ago
-
Three queries about the MS Outlook app on iPadOS
by 1 day, 22 hours ago
-
Win 10 22H2 November patches: Why do I have these 4 Windows App Runtime apps?
by 5 hours, 12 minutes ago
-
KB5032278
by 12 hours, 59 minutes ago
-
A web browser security testing & privacy testing tool.
by 2 days, 8 hours ago
-
IOS 17.1.2 looses text alert tone
by 1 day, 21 hours ago
-
What to know about CentOS Linux EOL
by 17 hours, 53 minutes ago
-
ESU announcement coming?
by 15 hours, 8 minutes ago
-
December 2023 Office non-Security Updates
by 2 days, 9 hours ago
-
Widespread Printer Bug caused by Windows Store!
by 19 hours, 58 minutes ago
-
Xbox question
by 2 days, 16 hours ago
-
Unfound Updates
by 2 days, 13 hours ago
-
Thieves rob DC Uber Eats driver, reject Android phone for not being iPhone
by 2 days, 14 hours ago
-
McAfee popup add (from micro. Store)
by 2 days, 16 hours ago
-
Random Screen Shut Downs (Windows 11 Pro)
by 1 day, 3 hours ago
-
CPU performance degradation after 23H2 update
by 3 days, 4 hours ago
