PowerShell Script to Detect Code Impacted by the Invoke-WebRequest Breaking Change

pwshguy (mdowst)M to

Powershell · 1 month ago

The recent breaking change to Invoke-WebRequest in Windows PowerShell 5.1 has the potential to affect a lot of automation, especially in older environments. To make it easier to assess the impact, I published a script called Search-CmdletParameterUsage.ps1.

This tool recursively scans your scripts and modules for any cmdlet + parameter usage. While I built it to identify places where Invoke-WebRequest is not using -UseBasicParsing, it works generically for any cmdlet you’re concerned about.

If you maintain large codebases or inherited automation, this can save a ton of manual review.

Script: https://gist.github.com/mdowst/9d00ff37ea79dcbfb98e6de580cbedbe

KB on the breaking change: https://support.microsoft.com/en-us/topic/powershell-5-1-preventing-script-execution-from-web-content-7cb95559-655e-43fd-a8bd-ceef2406b705

Happy scripting! And good luck hunting down those IWR calls.

You must log in or # to comment.

Chat

Powershell

powershell

Create a post

You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: [email protected]

PowerShell (POSH) is a a task automation command-line shell and scripting language created by Microsoft. It became part of the FOSS community in 2016 and is now available across Windows, Linux, and macOS

Resources:

Install PowerShell – Instructions for Windows, Linux, and macOS
PowerShell Galley Your one-stop shop community and Microsoft modules.
PowerShell Repository – View the PowerShell source code, report issues, or contribute to the project yourself.
PowerShell Community Call – Hear from and talk directly to the product team on the 3rd Thursday of every month
PowerShell in Visual Studio Code – It’s time to say goodbye to ISE

Rules:

Be civil (aka don’t be a jerk). Remember there are people from all walks of life, all with different levels of expertise. You can disagree with someone, but please be civil when doing so.
Adhere to the Lemmy Code of Conduct
Follow all programming.dev rules
Posts must relate to PowerShell or the PowerShell ecosystem.
Use code blocks to make things easier to read.
Memes and humorous posts are allowed but try not over do it. And keep them relevant to PowerShell
No discussion about piracy or hacking.
If someone provides an answer that solves your problem, please reply, so others know what the solution was. ^And ^so ^the ^person ^who ^suggested ^it ^gets ^that ^oh ^so ^sweet ^shot ^of ^dopamine.
If you find a solution to your problem by other means, please take your time to write down the steps you used to solve your problem in the original post. You can potentially help others having the same problem!

Self-promotion rules:

Self-promotion content must be marked as [OC]
Do not SPAM. Content must be PowerShell related.
Only 10% of your contributions can be self-promotion. In other words, 90% of your contribution must not be self-promotion.
Personal blogs are not considered self-promotion, at this time, as long as they are free to access and relevant. Please do not abuse this.

Visibility: Public

This community can be federated to other instances and be posted/commented in by their users.

1 user / day
6 users / week
10 users / month
47 users / 6 months
242 local subscribers
1.21K subscribers
147 Posts
117 Comments
Modlog