Ironman Software Forums
Continue the conversion on the Ironman Software forums. Chat with over 1000 users about PowerShell, PowerShell Universal, and PowerShell Pro Tools.
Recent versions of PowerShell Universal are affected by an authorization bypass issue and it is recommended that you update your environment.
A bug in the authorization logic for PowerShell Universal exposes APIs and Dashboards that enforce roles to any authenticated user. This issue will be present when using challenge-based authentication like OpenID Connect, WS-Federation, SAML2 and Windows Authentication. Forms authentication and JWT tokens are not affected by this issue.
Authentication is still required to access secure endpoints and dashboards.
For example, any user that can authenticate against this PowerShell Universal instance will be able to execute this endpoint, regardless of role.
New-PSUEndpoint -Url '/secure' -Endpoint {
"ack"
} -Authenticated -Role 'Administrator'
This will bypass authorization but authentication is still necessary.
Invoke-RestMethod https://localhost:5001/secure -UseDefaultCredentials
This will return a 401 error code.
Invoke-RestMethod https://localhost:5001/secure
The following versions are affected.
To mitigate this issue, you must upgrade to PowerShell Universal 2.7.4 or later.
Downloads are available from our website.
Continue the conversion on the Ironman Software forums. Chat with over 1000 users about PowerShell, PowerShell Universal, and PowerShell Pro Tools.
Receive once-a-month updates about Ironman Software. You'll learn about our product updates and blogs related to PowerShell.