This is based on an issue, where Enter-PSHostProcess on a locked down (WDAC enforced) machine allows any admin to connect to any another local hosted PowerShell process and execute commands as that user. This amounts to privilege escalation on the policy locked down machine and something we want to prevent. Fix is to check for system lock down and disable Enter-PSHostProcess cmdlet with an error message. |
||
---|---|---|
.. | ||
Modules | ||
TestData/CatalogTestData | ||
AclCmdlets.Tests.ps1 | ||
AmsiInterface.Tests.ps1 | ||
certificateCommon.psm1 | ||
CertificateProvider.Tests.ps1 | ||
CmsMessage.Tests.ps1 | ||
ConstrainedLanguageDebugger.Tests.ps1 | ||
ConstrainedLanguageModules.Tests.ps1 | ||
ConstrainedLanguageRestriction.Tests.ps1 | ||
ConstrainedLanguageValidation.Tests.ps1 | ||
ExecutionPolicy.Tests.ps1 | ||
FileCatalog.Tests.ps1 | ||
GetCredential.Tests.ps1 | ||
SecureString.Tests.ps1 |