๐ย Secure Bits ๐ก
๐ง๐ต๐ถ๐ป๐ธ ๐ฅ๐๐ฃ + ๐๐ฟ๐ฒ๐ฑ๐ฒ๐ป๐๐ถ๐ฎ๐น ๐๐๐ฎ๐ฟ๐ฑ ๐ธ๐ฒ๐ฒ๐ฝ๐ ๐๐ผ๐๐ฟ ๐ฑ๐ผ๐บ๐ฎ๐ถ๐ป ๐ฎ๐ฑ๐บ๐ถ๐ป ๐ฐ๐ฟ๐ฒ๐ฑ๐ ๐๐ฎ๐ณ๐ฒ? ๐ก๐ผ๐ ๐ฟ๐ฒ๐ฎ๐น๐น๐.
Even in 2025,ย many ๐ฎ๐ฑ๐บ๐ถ๐ป๐ ๐๐๐ถ๐น๐น ๐ฒ๐ ๐ฝ๐ผ๐๐ฒ ๐๐ต๐ฒ๐ถ๐ฟ ๐๐ผ๐บ๐ฎ๐ถ๐ป ๐๐ฑ๐บ๐ถ๐ป ๐ฐ๐ฟ๐ฒ๐ฑ๐ฒ๐ป๐๐ถ๐ฎ๐น๐ย without realizing it โ just by using RDP to access Domain Controllers from their regular workstation.
๐ง ย โBut Iโve got ๐๐ฟ๐ฒ๐ฑ๐ฒ๐ป๐๐ถ๐ฎ๐น ๐๐๐ฎ๐ฟ๐ฑ, Iโm protected!โ
Not always.
๐๐ฒ๐ฟ๐ฒโ๐ ๐๐ต๐ฎ๐ ๐ฎ๐ฐ๐๐๐ฎ๐น๐น๐ ๐ต๐ฎ๐ฝ๐ฝ๐ฒ๐ป๐ย ๐ถ๐ป ๐ฐ๐ฎ๐๐ฒ ๐ผ๐ณ ๐ฅ๐๐ฃ:
1๏ธโฃ You connect to a DC via RDP from your “basic ” machine
2๏ธโฃ As part of that RDP session,ย your password gets cached in MSTSC memory
3๏ธโฃ An attacker on your workstation could extract it โย even in plaintext
๐ฅ ๐๐ฟ๐ฒ๐ฑ๐ฒ๐ป๐๐ถ๐ฎ๐น ๐๐๐ฎ๐ฟ๐ฑ ๐ฑ๐ผ๐ฒ๐๐ปโ๐ ๐๐ฎ๐๐ฒ ๐๐ผ๐ ๐ต๐ฒ๐ฟ๐ฒ.
Neither will SmartCards (care to guess what ends up in memory instead?)
๐ฏ The real fix? Implement ๐ฝ๐ฟ๐ผ๐ฝ๐ฒ๐ฟ ๐ฃ๐ฟ๐ถ๐๐ถ๐น๐ฒ๐ด๐ฒ๐ฑ ๐๐ฐ๐ฐ๐ฒ๐๐ ๐ช๐ผ๐ฟ๐ธ๐๐๐ฎ๐๐ถ๐ผ๐ป๐ (๐ฃ๐๐ช) ๐ฎ๐ป๐ฑ ๐ณ๐ผ๐น๐น๐ผ๐ ๐๐ต๐ฒ ๐ง๐ถ๐ฒ๐ฟ๐ถ๐ป๐ด ๐ ๐ผ๐ฑ๐ฒ๐น. You can also take advantage of Restricted Admin Mode in RDP, but it requires the knowledge of the above.
Your credentials are only as secure as the device you log in from.
๐ Ever tested what MSTSC leaks in memory?
