Microsoft.PowerShell.Commands.Utility is vulnerable to Incorrect Authorization
50
CVE Score
Medium
Incorrect Authorization
The entry point is AddRemoteCommandMetadata in ImplicitRemotingCommands.cs, which builds proxies when Import-PSSession or Export-PSSession imports commands from a PSSession. Before the fix, IsSafeNameOrIdentifier, IsCommandSkippedByServerDeclaration, and IsCommandNameAllowedForImport ran only against commandMetadata.Name, and the method then stored the command under resolvedCommandName. A remote alias could therefore pass those checks under an innocuous name and be stored as the resolved command, including a skip-listed command such as Get-Help or a local command such as PSConsoleHostReadLine, even when -AllowClobber was not set. The console host calls PSConsoleHostReadLine to read the next line and runs the string that proxy returns.
Upgrade the Microsoft.PowerShell.Commands.Utility library to the patch version.
You are affected if you are using a version that falls within the vulnerable range and you use Import-PSSession or Export-PSSession to generate implicit remoting proxy modules from a remote session that defines command aliases.
6.0.4 - 7.4.20
Fixed in 7.4.217.5.0 - 7.5.11
Fixed in 7.5.127.6.0 - 7.6.6
Fixed in 7.6.7Microsoft.PowerShell.Commands.Utility is vulnerable to Incorrect Authorization in versions 6.0.4 - 7.4.20, 7.5.0 - 7.5.11 and 7.6.0 - 7.6.6.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.