Earlier quoted context omitted.
Or perhaps, once someone installs untrusted software in the first place, you’re screwed anyway? This is security 101. AFAIK, you can login as a local admin since forever and it’s never been fixed. I just used it recently to access a deceased relative’s computer.
I was surprised to find that a modern windows 10 machine (with all default security options) could have the user password bypassed easily with a Windows setup USB. I could then read all the user's documents. I thought the point of disk encryption and secure boot was to prevent that. Yet somehow the hole of allowing Windows setup to give you a privileged command prompt with a decrypted disk was never closed...
HiveNightmare a.k.a. SeriousSAM – anybody can read the registry in Windows 10
21–30 of 184 posts
Re: HiveNightmare a.k.a. SeriousSAM – anybody can read the registry in Windows 10
#22Some Windows configuration have bad permissions on their SAM database. If a standard user has access to shadow copies (VSS), this can lead to privilege escalation.
Microsoft recommends to [1]:
1) Restrict access to the contents of %windir%\system32\config: - Command Prompt (Run as administrator): icacls %windir%\system32\config*.* /inheritance:e - Windows PowerShell (Run as administrator): icacls $env:windir\system32\config*.* /inheritance:e
2) Delete Volume Shadow Copy Service (VSS) shadow copies: - Delete any System Restore points and Shadow volumes that existed prior to restricting access to %windir%\system32\config. - Create a new System Restore point (if desired).
--
Also, please note that some authorities seem to adress this subject carefully. The French national cybersecurity agency (ANSSI) has for instance published a News bulletin [2] but no "real" Security bulletin of this vulnerability [3].
In its News bulletin, the ANSSI specifies that it also affects Windows Vista RTM :).
However, the ANSSI also says that deleting VSS entries (step 2 of Microsoft recommendations) "must be decided after evaluating the advantages and disadvantages with regard to the risks, in particular because there may be other possibilities for privilege escalation depending on the level of security of your information system."
[1] https://msrc.microsoft.com/update-guide/vulnerability/CVE-20...
[2] https://www.cert.ssi.gouv.fr/actualite/CERTFR-2021-ACT-031/
Re: HiveNightmare a.k.a. SeriousSAM – anybody can read the registry in Windows 10
#23I'll take all the side-channels I can get though. These "exploits" are really useful for regaining control over my own PC.
Just yesterday I learned how to Run-As TrustedInstaller, and that let me remove a lot of unwanted bullshit on my windows 10 install.
Re: HiveNightmare a.k.a. SeriousSAM – anybody can read the registry in Windows 10
#24https://rwmj.wordpress.com/2010/02/18/why-the-windows-regist...
Re: HiveNightmare a.k.a. SeriousSAM – anybody can read the registry in Windows 10
#25So one of the most wonderful things about relying on their proprietary closed source operating system is that you can't have external code audits. You just kind of wait for ethical people to come forward and explain bugs they've found and wonder, 1, how long has it been there, 2, how long have bad actors known about this, 3, how many other bugs are just like this or worse that they haven't found yet, 4, do I need to…
Microsoft Windows is proprietary software yes, but they have something called the Shared Source Initiative. > Through the Shared Source Initiative Microsoft licenses product source code to qualified customers, enterprises, governments, and partners for debugging and reference purposes. https://www.microsoft.com/en-us/sharedsource/ I say this as someone who doesn’t like Windows and doesn’t run Windows. We still need t…
Re: HiveNightmare a.k.a. SeriousSAM – anybody can read the registry in Windows 10
#26It amazes me that Microsoft haven't replaced the Registry with a simple directory structure, not that it would help for this particular bug, but it would surely be an improvement. I maintain a library for accessing the registry from Linux ( https://github.com/libguestfs/hivex ) and after writing it I also wrote this screed about how it sucks in just about every way possible: https://rwmj.wordpress.com/2010/02/18/why-…
Actually you can use the Windows Projected File System to project the registry into the file system, making registry keys and values appear as files and directories.
https://github.com/Microsoft/Windows-classic-samples/tree/ma...
Re: HiveNightmare a.k.a. SeriousSAM – anybody can read the registry in Windows 10
#27So one of the most wonderful things about relying on their proprietary closed source operating system is that you can't have external code audits. You just kind of wait for ethical people to come forward and explain bugs they've found and wonder, 1, how long has it been there, 2, how long have bad actors known about this, 3, how many other bugs are just like this or worse that they haven't found yet, 4, do I need to…
Microsoft Windows is proprietary software yes, but they have something called the Shared Source Initiative. > Through the Shared Source Initiative Microsoft licenses product source code to qualified customers, enterprises, governments, and partners for debugging and reference purposes. https://www.microsoft.com/en-us/sharedsource/ I say this as someone who doesn’t like Windows and doesn’t run Windows. We still need t…
Re: HiveNightmare a.k.a. SeriousSAM – anybody can read the registry in Windows 10
#28> There’s no patches, it’s a zero day. Seems that MS just released articles on how to prevent it but no update/patch. Perhaps it's hard to fix, i.e., too many things on windows rely on it?
Re: HiveNightmare a.k.a. SeriousSAM – anybody can read the registry in Windows 10
#29Earlier quoted context omitted.
Or perhaps, once someone installs untrusted software in the first place, you’re screwed anyway? This is security 101. AFAIK, you can login as a local admin since forever and it’s never been fixed. I just used it recently to access a deceased relative’s computer.
I was surprised to find that a modern windows 10 machine (with all default security options) could have the user password bypassed easily with a Windows setup USB. I could then read all the user's documents. I thought the point of disk encryption and secure boot was to prevent that. Yet somehow the hole of allowing Windows setup to give you a privileged command prompt with a decrypted disk was never closed...
Default options do not enable any drive encryption Secure boot is as the name says something to make booting secure it has absolutely nothing to do with protecting data on disk from being accessed by someone with physical access to the machine.
Re: HiveNightmare a.k.a. SeriousSAM – anybody can read the registry in Windows 10
#30Earlier quoted context omitted.
Microsoft Windows is proprietary software yes, but they have something called the Shared Source Initiative. > Through the Shared Source Initiative Microsoft licenses product source code to qualified customers, enterprises, governments, and partners for debugging and reference purposes. https://www.microsoft.com/en-us/sharedsource/ I say this as someone who doesn’t like Windows and doesn’t run Windows. We still need t…
The key question is: would they let people who want to find bugs? Because that is the point here, if you can read the software but not allowed to do an audit, it doesn't make any difference (for the issue that we're discussing).
Allowed purposes for said licensing program includes “performing internal security audits of the Microsoft Windows operating system”.