Add blog and 2.7 changelog

blog/2024-09-06-Keyhole/index.md

@@ -0,0 +1,166 @@
+---
+slug: keyhole
+title: Keyhole
+authors: [witherornot, may]
+tags:
+  - Windows
+  - Activation
+---
+
+# Keyhole
+
+By WitherOrNot  
+Edited by May, Lyssa & SpCreatePackaedLicense
+
+## Introduction
+
+In our ongoing work to bypass Windows licensing checks, we occasionally stumble upon bugs that, rather than sharing details about publicly, we choose to keep under wraps. This decision allows us to preserve potential future activation methods by avoiding bug fixes being made by Microsoft, while also giving us valuable tools for testing or developing new methods. 
+
+One such discovery, which we’ve dubbed "Keyhole", turned out to be a highly effective DRM bypass. It gave users the ability to license any Microsoft Store app or any modern Windows edition with ease.
+
+<!-- truncate -->
+
+Following the disclosure of [CVE-2024-38184](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-38184) by [Cisco TALOS](https://talosintelligence.com), we have decided to share our findings on Keyhole, which we independently uncovered around the same time it's existence became known to Microsoft.
+
+## CLiP
+
+To understand this exploit, we must first understand CLiP, the Client Licensing Platform. This system was introduced with Windows 10, primarily as a way to implement DRM for Microsoft Store apps, and integrated with Windows activation, allowing users to buy digital licenses for Windows on the Microsoft Store.
+
+CLiP is comprised of a few different main binaries within Windows:
+ - `clipup.exe` - Migrates (converts) Windows 8 store licenses, genuine tickets, and product keys to digital licenses
+ - `clipsvc.dll` - User-mode service responsible for managing app licenses
+ - `clipc.dll` - API used by applications to interact with CLiP
+ - `clipwinrt.dll` - Similar to `clipc.dll` but for UWP applications utilizing [Windows Runtime](https://learn.microsoft.com/en-us/windows/uwp/winrt-components).
+ - `clipsp.sys` - Kernel-mode driver responsible for verifying licenses
+
+![clip diagram](./assets/keyhole/clip_diagram.png)
+
+Whenever a CLiP-licensed app is installed, a signed XML file containing the license information is sent to `clipsvc.dll`; once the XML signature is verified, the XML data is stored in ClipSVC's "physical store" at `%PROGRAMDATA%\Microsoft\Windows\ClipSVC\tokens.dat`. 
+
+The signed license block is then extracted from the `SPLicenseBlock` tag and sent to `clipsp.sys` for verification. After verification, the license block is deposited in the CLiP license store at `HKLM\SYSTEM\CurrentControlSet\Control\{7746D80F-97E0-4E26-9543-26B41FC22F79}`. From there, `clipsp.sys` can then re-validate the license in the future if an app requests it using the CLiP API.
+
+> [!NOTE]
+> The CLiP license store mentioned earlier is protected so that you can't view it by default but changing the permissions to allow yourself access is very easy.
+
+As designed, this system forms a rather strong chain-of-trust that transmits only signed data from usermode applications all the way to the kernel, making it seemingly difficult to tamper with. As we will see soon, however, this is not at all the case.
+
+## A Little Trolling
+
+So far, one binary failed to receive any mention: `clipup.exe`. This is because it isn't notable when talking about Keyhole itself. However, it holds the key to messing with CLiP:
+
+![ecc key](./assets/keyhole/ecc_key.png)
+
+Yes, literally. A valid ECDSA key to sign XML licenses is stored in unobfuscated form, allowing anyone to very easily sign or resign XML licenses. This allows us to bypass ClipSvc's gatekeeping and effectively send any license blocks we want straight to ClipSp. With this, we entirely bypass the usermode level of the chain-of-trust, and now all that's left is to try and trick ClipSp.
+
+## Unpacking ClipSp
+
+ClipSp, from our analysis, is not a very well-written driver. It's full of copy-pasted code (from where will be shown soon), and seems to be rife with odd choices and compromises. In other words, it's a perfect environment for someone looking for a bypass. There's only one big issue: most of the interesting driver code is hidden using Microsoft's proprietary obfuscator, known as Warbird. In order to find and understand it, we need to "unpack" it, a.k.a. undoing the obfuscation. Luckily, this is rather straightforward thanks to some symbols for `clipsp.sys` that were available on Microsoft's servers.
+
+Similar to how Warbird works [in user-mode programs](https://github.com/WitherOrNot/warbird-docs), ClipSp wraps any calls to obfuscated code with an decryption and encryption function, as shown below:
+
+![feistel wrapper](./assets/keyhole/encrypt_decrypt.png)
+
+So, if we can manually run these decryption functions, we could access all of the hidden code. Luckily, this is quite simple to do based on a method [by KiFilterFiberContext](https://github.com/KiFilterFiberContext/warbird-hook), and with it, we are now able to finally find some bugs.
+
+## License Blocks
+
+License blocks, mentioned previously, are what actually hold the important license information in CLiP. Their format is [well-documented](https://github.com/LukeFZ/CikExtractor) and can store many kinds of data, so we figured they were a good place to start looking for bugs.
+
+License blocks hold their data in a tag-length-value (TLV) format, where several smaller blocks are stored together with each holding values for their data type, the length of their data, and the data itself. For example, the TLV block highlighted below has a type of `0xC9` (License Information), a length of `0xA` (10 bytes), and 10 bytes of data.
+
+![splicenseblock tlv](./assets/keyhole/tlv_example.png)
+
+At the very end of a license block, there will always be a signature block, with a type of `0xCC`. This block holds the signature of all the data before it, as well as indicating which key it was signed with. And of course, since it sits after all the data being signed, there's no way to alter any of it... right?
+
+## A Lot of Trolling
+
+In the middle of experimenting with this data format, one of our members, May, had a very simple question. If the signature block signs all the data before it, what happens to the data put after it?
+
+![image](./assets/keyhole/test_keyhole.png)
+
+Above, you can see a license block for Minecraft Bedrock edition with some new data placed after it (highlighted), containing blocks copied from a Windows license. What happens if we try to install such a license?
+
+![enterprise ltsc digital activation](./assets/keyhole/enterprises_diglic.png)
+
+As it turns out, data after the signature block isnt checked at all... and it can even override data that came before it. Whenever two blocks of the same type are stored together, the last one overrides all the others before it. So, if we want to change any license data, we can just make a block for it and put it after the signature block!
+
+This method lets us make licenses for anything sold on the Microsoft Store, including Windows, from any other Microsoft Store license. And since there are so many free apps with licenses, we now had the ability to make as many as we wanted for whatever we wanted. This bug essentially punched a hole straight through CLiP's DRM, so we decided to name it "Keyhole".
+
+There is only one catch: licenses that are bound to a specific device, known as "device-locked" licenses, cannot be made from device-unlocked licenses. Since Windows digital licenses are device-locked, this meant that we needed to make them from device-locked app licenses. Luckily, many apps, including games like Roblox fit this criteria.
+
+## Trolling Tutorial
+
+The steps to make any Windows license you want were now dead simple. First, install an app with a device-locked license, like Roblox.
+
+![roblox](./assets/keyhole/step1.png)
+
+Then, using a HTTPS traffic capture tool like Fiddler, intercept the license that comes from `https://licensing.mp.microsoft.com/v7.0/licenses/content`.
+
+![fiddler](./assets/keyhole/step2.png)
+
+Decode the license, then extract its license block.
+
+![license block](./assets/keyhole/step3.png)
+
+Now, add whatever new data you need to make a new license.
+
+![add keyholed data](./assets/keyhole/step4.png)
+
+Then, we just package our license block into a new XML file, sign the XML, and copy it into the folder `C:\ProgramData\Microsoft\Windows\ClipSVC\Install\Migration`.
+
+![license in migration folder](./assets/keyhole/step5.png)
+
+Finally, we get ClipSvc to install our license, either by restarting it, or with the command `clipup -p`.
+
+![clipup -p in cmd](./assets/keyhole/step6.png)
+
+When we check our activation status, Windows is now permanently activated.
+
+![server is digitally licensed](./assets/keyhole/step7.png)
+
+With this, we were able to do things that were previously impossible, like activating Enterprise LTSC with a digital license, or even activating a legitimate KMS server with a generic key:
+
+![26100 kms server](./assets/keyhole/trivial.png)
+
+From here, it's pretty easy to see that this simple bug completely annihilates CLiP's DRM system.
+
+## Buzzkill
+
+Having found this bug, we were quite happy that CLiP was now effectively dead. This happiness didn't last very long, though, as we recently found a [vulnerability report](https://talosintelligence.com/vulnerability_reports/TALOS-2024-1964) from Cisco TALOS that reported this exact bug. It was reported to Microsoft on April 8, right around when we first found it.
+
+![keyhole discovery](./assets/keyhole/kh_discovery.png)
+
+For some reason beyond us, they reported it as a "privilege escalation", even though editing CLiP licenses does little to grant an attacker more access to a system. As we view it, this was just an excuse for TALOS to report this DRM bug along with [other more serious bugs in ClipSp](https://talosintelligence.com/vulnerability_reports/TALOS-2024-1988).
+
+What did they get out of this? We have no idea, and seemingly it looks like they didn't get anything in return, aside from a minor credit in the [August 2024 update release notes](https://msrc.microsoft.com/update-guide/releaseNote/2024-Aug). So, to Philippe Laulheret who reported this bug, I hope you feel good about ruining our fun for a 4-months-late pat on the back.
+
+## Giving Season
+
+After mourning the loss of our beloved exploit, we decided that it would only be fair to publicize our own discoveries on CLiP. So, we've released the code to [generate Keyhole licenses](https://github.com/massgravel/keyhole) and our [collection of CLiP binaries](https://archive.org/details/clipwinrt) with symbols for easier analysis. We invite you to go forth and discover more funny things in CLiP! (and [report them to us](https://massgrave.dev/contactus) instead of MS)
+
+## And now, for something different
+
+I mentioned that ClipSp's buggy code was copy-pasted, but from where? Well, the "SP" part just happens to reference a certain Microsoft game console: the Xbox One!
+
+The Xbox One contains a chip known as the SP, or "secure processor", based on the TPMs in modern PCs. The main job of the SP is to enforce code signing, but it also handles license verification. During our research on Keyhole, we found many associations between CLiP and the Xbox One, and began wondering how they were actually related. While looking through some leaked source code, we stumbled upon this:
+
+![ValidateLicensePolicy](./assets/keyhole/validatelicensepolicy.png)
+
+Well, this looks oddly familiar...
+
+![keyhole bug in source code](./assets/keyhole/src_bug.png)
+
+And there's the same bug that's in CLiP, but in Xbox code. In fact, we weren't too surprised to find this, as we found that almost all of CLiP, from the XML format of the licenses to the TLV-based license blocks, is copy-pasted straight from the Xbox One's DRM system.
+
+So, to those with a console that's been [collaterally damaged](https://github.com/exploits-forsale/collateral-damage), I wonder what happens if you mess with those funny-looking XML files in `S:\clip` ;)
+
+## Credits
+
+The research covered in this blogpost was made possible by the following people/groups:
+
+ - May - Initial discovery, testing, reverse engineering
+ - SpCreatePackaedLicense, asdcorp - Further testing, reverse engineering
+ - WitherOrNot - Tool development, testing, reverse engineering
+ - emoose, LukeFZ - License Block format documentation
+ - KiFilterFiberContext - ClipSp unpacking
+ - Phillippe Laulheret, Cisco TALOS - Inspiring this publication

blog/authors.yml

@@ -0,0 +1,19 @@
+witherornot:
+  name: WitherOrNot
+  title: Researcher @ MASSGRAVE
+  url: https://github.com/WitherOrNot
+  image_url: https://avatars.githubusercontent.com/u/26913821
+  page: true
+  socials:
+    github: WitherOrNot
+    x: witherornot1337
+
+may:
+  name: May
+  title: Researcher @ MASSGRAVE
+  url: https://github.com/ave9858
+  image_url: https://avatars.githubusercontent.com/u/112294121
+  page: true
+  socials:
+    github: ave9858
+

blog/tags.yml

@@ -0,0 +1,19 @@
+facebook:
+  label: Facebook
+  permalink: /facebook
+  description: Facebook tag description
+
+hello:
+  label: Hello
+  permalink: /hello
+  description: Hello tag description
+
+docusaurus:
+  label: Docusaurus
+  permalink: /docusaurus
+  description: Docusaurus tag description
+
+hola:
+  label: Hola
+  permalink: /hola
+  description: Hola tag description

docs/changelog.md

@@ -2,6 +2,94 @@
 
 ------------------------------------------------------------------------
 
+## 2.7
+
+**A new change Office edition script, rewritten Online KMS script and lots of improvements**
+
+#### All:
+
+- Removed dependancy on [WMIC](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/wmi-command-line-wmic-utility-deprecation-next-steps/ba-p/4039242) and [VBScript](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/vbscript-deprecation-timelines-and-next-steps/ba-p/4148301).
+- Added the check for [Windows subscription](https://learn.microsoft.com/windows/deployment/windows-subscription-activation?pivots=windows-11), activation will be performed based on base edition, [example](https://i.imgur.com/6LTkK2o.png). Thanks to asdcorp and @abbodi1406.
+- Added the code to disable CMD QuickEdit using Powershell instead of temporary regedit (to avoid accidental pause when the user clicks inside the script window). Thanks to @abbodi1406.
+- Added the code to launch from conhost.exe using Powershell to avoid the Terminal app. Thanks to @abbodi1406.
+- Added more environment variables in the script at the start to resolve issues in case they are messed up in the user's system.
+- Added debug mode option in separate files version to create a log file with details.
+- Added better check in Powershell execution without crashing the script in case any antivirus is blocking it.
+- Added better SPP check at the start to find issues where the script just hangs without any output, now it will show an error after waiting a certain time.
+- Changed messages related to eval edition activation.
+- Reduced the number of services to check health to a bare minimum.
+- Added SPP trigger reevaluation command at the end of the activation, it helps in updating SPP tasks.
+- Added the command to delete SuppressRulesEngine registry keys by default in every run if found, this causes issues in spp tasks to refresh.
+- Added the extra checks for malware and showed info accordingly.
+- Added better error handling of SPP 2.0 folder creation.
+- Added better check to find [permission issues](https://learn.microsoft.com/office/troubleshoot/activation/license-issue-when-start-office-application) in SPP.
+- Added the command to check SvcRestartTask Status to find potential activation issues.
+- Updated the WPA registry check code to skip unrelated keys, and to make it work on Windows 7 as well.
+- Added the code to show the option to open the Troubleshoot page if errors are found.
+- Many other small changes to better handle errors.
+
+#### HWID / KMS38
+
+- Removed the extra checks for Windows update services and replaced them with a more accurate check in S-1-5-19 IdentityCRL registry to find connection errors.  
+  Now Update service error will only be shown when it's very likely to be a cause for the activation failure.
+
+#### KMS38
+
+- Update Windows Server 2025 keys to use from products.ini
+
+#### Ohook
+
+- Added the code to add SharedComputerLicensing registry to avoid [licensing issues](https://learn.microsoft.com/office/troubleshoot/office-suite-issues/click-to-run-office-on-terminal-server) in the case of Windows Server with Retail C2R office.
+- Script will now skip installing the key for already activated products.
+- Added the info for the Office version and the update channel.
+- Script will fix ProductReleaseIds In Registry if incorrect found, it affects features.
+- Script will check the running Office apps and will ask to close them before proceeding.
+- Added more detailed info in case Ohook installation fails.
+- Added more accurate detection of MSI Office products.
+- Script will now deeply find remnants of Office [vNext](https://learn.microsoft.com/office/troubleshoot/activation/reset-office-365-proplus-activation-state)/[shared](https://learn.microsoft.com/en-us/deployoffice/overview-shared-computer-activation)/[device](https://learn.microsoft.com/deployoffice/device-based-licensing)/[OEM](https://support.microsoft.com/office/office-repeatedly-prompts-you-to-activate-on-a-new-pc-a9a6b05f-f6ce-4d1f-8d49-eb5007b64ba1) license block, and will clean them.
+- Script will now add a Resiliency key to avoid the licensing banner in all of the user accounts including those that are not logged in, also registry will be added to all new future user accounts.
+- Script is updated to use [Ohook 0.5 (non+ version)](https://github.com/asdcorp/ohook), nothing is changed functionality-wise, you don't need to update your already installed Ohook.
+
+#### Online KMS
+
+- Rewrote the whole thing from scratch. Thanks to @abbodi1406 for the help.  
+Difference from the previous version:
+- Added the option to set the KMS server/port.
+- Added support for Office 2024.
+- Script will show the option to activate Office (All) and Office (Project/Visio) and the script won't skip the already activated Office products.
+- Toggle option is added to install the Renewal task along with the activation, by default it's set to install the renewal task along with activation.
+- Script will create a run-once task if the Internet is not found, which will run on system login if the Internet is found later.
+- Toggle option is added to not change edition if needed for Windows/Office.
+- Added more info on the screen regarding the process.
+
+#### Change Office Edition
+
+- This is a [new option](change_office_edition.md) added in the script.
+- It offers the option to change the installed C2R Office edition to any other with minimum Internet consumption. Thanks to @ave9858 for the suggestion.
+- It also offers the option to change the Office update channel. Thanks to @abbodi1406.
+
+#### Change Windows Edition
+
+- This script will now create log files on the desktop in case if edition change fails.
+- Several bugs fixed.
+
+#### Check Activation Status
+
+- Previous scripts are now replaced with [CAS](https://gravesoft.dev/cas) by @abbodi1406.
+
+#### Troubleshoot
+
+- Added the code to fix activation errors caused by [KB971033](https://support.microsoft.com/help/4487266) in Windows 7.
+- Removed the unnecessary code to find errors because they are already in activation scripts.
+
+#### Misc
+
+- MASSGRAVE blog page is now [available](/blog).
+- Offical support email ID is changed to `mas.help@outlook.com` due to some issues from receiving emails from China on Protonmail.
+- A new mirror repo is opened on [Codeberg](https://codeberg.org/massgravel/Microsoft-Activation-Scripts).
+
+------------------------------------------------------------------------
+
 ## 2.6
 
 **Added Support For Office 2024**

docs/ohook.md

@@ -255,15 +255,15 @@ TL;DR all kinds of Office products are supported on Windows 8 and higher and the
 
 ## Custom sppc.dll Info
 
--   Custom sppc.dll source code (Ohook 0.3) is available [here](https://github.com/asdcorp/ohook/archive/refs/tags/0.3.zip).
+-   Custom sppc.dll source code (Ohook 0.5) is available [here](https://github.com/asdcorp/ohook/archive/refs/tags/0.5.zip).
 -   SHA-256 checksums:  
 ```         
-e6ac83560c19ec7eb868c50ea97ea0ed5632a397a9f43c17e24e6de4a694d118 *sppc32.dll
-c6df24deef2e83813dee9c81ddd9793a3d60c117a4e8e231b82e32b3192927e7 *sppc64.dll
+09865ea5993215965e8f27a74b8a41d15fd0f60f5f404cb7a8b3c7757acdab02 *sppc32.dll
+393a1fa26deb3663854e41f2b687c188a9eacd87b23f17ea09422c4715cb5a9f *sppc64.dll
 ```
 -   In MAS AIO version, these 2 files are encoded in base64 to make MAS AIO version. In AIO script, [instructions](https://stackoverflow.com/a/35335273) are mentioned on how to decode files from Base64 format.  
 **How to create identical sppc.dll files from scratch?**  
--   Download ohook 0.3 source code file from [here](https://github.com/asdcorp/ohook/archive/refs/tags/0.3.zip)
+-   Download ohook 0.5 source code file from [here](https://github.com/asdcorp/ohook/archive/refs/tags/0.5.zip)
 -   Extract this zip file to a folder named `C:\ohook`
 -   Now download these two compiler archives, [mingw32](https://github.com/brechtsanders/winlibs_mingw/releases/download/11.4.0-11.0.0-ucrt-r1/winlibs-i686-posix-dwarf-gcc-11.4.0-mingw-w64ucrt-11.0.0-r1.7z) and [mingw64](https://github.com/brechtsanders/winlibs_mingw/releases/download/11.4.0-11.0.0-ucrt-r1/winlibs-x86_64-posix-seh-gcc-11.4.0-mingw-w64ucrt-11.0.0-r1.7z)
 -   Extract both archives with 7-zip in C drive, so that path would look like this,  

docusaurus.config.js

@@ -48,7 +48,21 @@ const config = {
           editUrl:
             'https://github.com/massgravel/massgrave.dev/tree/main/',
         },
-        blog: false,
+        blog: {
+          showReadingTime: true,
+          feedOptions: {
+            type: ['rss', 'atom'],
+            xslt: true,
+          },
+          // Please change this to your repo.
+          // Remove this to remove the "edit this page" links.
+          editUrl:
+            'https://github.com/massgravel/massgrave.dev/tree/main/',
+          // Useful options to enforce blogging best practices
+          onInlineTags: 'warn',
+          onInlineAuthors: 'warn',
+          onUntruncatedBlogPosts: 'warn',
+        },
         theme: {
           customCss: './src/css/custom.css',
         },
@@ -98,12 +112,12 @@ const config = {
             position: 'left',
             label: 'Credits',
           },
+		  {to: '/blog', label: 'Blog', position: 'right'},
           {
             to: '/contactus',
             position: 'right',
             label: 'Contact Us',
           },
-          /* {to: '/blog', label: 'Blog', position: 'left'}, */
           {
             href: 'https://discord.gg/tVFN4N84PP',
             className: 'discord-button',