๐ Secure Bits ๐ก
๐๐ถ๐ฑ ๐๐ผ๐ ๐ธ๐ป๐ผ๐ ๐๐ผ๐ ๐ฐ๐ฎ๐ป ๐ต๐ฎ๐๐ฒ ๐ฎ ๐๐ผ๐บ๐ฝ๐๐๐ฒ๐ฟ ๐๐ฐ๐ฐ๐ผ๐๐ป๐ ๐๐ถ๐๐ต ๐ฎ “๐ธ๐ป๐ผ๐๐ป” ๐ฝ๐ฎ๐๐๐๐ผ๐ฟ๐ฑ ๐ถ๐ป ๐๐ฐ๐๐ถ๐๐ฒ ๐๐ถ๐ฟ๐ฒ๐ฐ๐๐ผ๐ฟ๐?
When you pre-create a domain computer account, you can check:
โ
โAssign this computer account as a pre-Windows 2000 computerโ
๐ช๐ต๐ฎ๐ ๐ฑ๐ผ๐ฒ๐ ๐๐ต๐ถ๐ ๐ฑ๐ผ?
It sets the computer account password based on the machine’s name:
โช๏ธTakes the sAMAccountName (without the trailing $)
โช๏ธTruncates it to the first 14 characters
โช๏ธConverts it to lowercase
โช๏ธThat becomes the password
๐ช๐ต๐ ๐๐ผ๐๐น๐ฑ ๐ฎ๐ป๐๐ผ๐ป๐ฒ ๐ฑ๐ผ ๐๐ต๐ถ๐?
Today, there’s almost no reason to use it.
But back in the day, pre-creating computer accounts via scripts was common, and this shortcut made automation easier.
๐ช๐ต๐ ๐ฑ๐ผ๐ฒ๐ ๐ถ๐ ๐บ๐ฎ๐๐๐ฒ๐ฟ ๐ป๐ผ๐?
If your Active Directory is old, thereโs a chance some accounts are still vulnerable. And yes โ attackers will check for this.
There are many small vulnerabilities like this hiding in Active Directory.
Always audit your environment.
The screenshot is from my tool โ ๐๐๐ฃ๐ฟ๐ผ๐ฏ๐ฒ โ a free, simple, and transparent PowerShell script. Feel free to use it however you like
๐https://academy.horizon-secured.com/p/adprobe
