System.Management.Automation vulnerabilities

Runtime for hosting PowerShell

Registry
NuGet
Latest
7.7.0
License
MIT

2 known advisories

The latest version, 7.7.0, is not affected by any of them. Projects on older versions may be.

Update to the latest version:dotnet add package System.Management.Automation --version 7.7.0

Is your project on an affected System.Management.Automation?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Security advisories for System.Management.Automation

  • HighCVE-2019-1301GHSA-62gw-3rmj-wmp213 Sept 2019

    High severity vulnerability that affects System.Management.Automation

    Affected
    >=6.2.0 <6.2.3 · >=6.0.0 <6.1.6
    Fixed in
    6.1.6, 6.2.3
  • MediumCVE-2019-1167GHSA-5frh-8cmj-gc5917 Jul 2019

    System.Management.Automation subject to bypass via script debugging

    Affected
    >=6.2.0 <6.2.2 · >=6.1.0 <6.1.5
    Fixed in
    6.1.5, 6.2.2

Is your System.Management.Automation version vulnerable?

Which of your client projects still run an old System.Management.Automation?

NPMscan reads the packages.lock.json and .csproj files in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Other NuGet packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the NuGet registry.