[r0x0r007]

That feeling when you open a brand new project in VS and immediately get: "The solution contains packages with vulnerabilities"

[CharlieDigital]

That's a Good Thing rather than shipping vulnerable code.

[Traubenfuchs]

It's pretty much the same in Javaland with maven and spring.

Create a new project with the latest spring version, and maven will warn you.

At this point I consider this worthless noise.

[weinzierl]

I think Spring doesn't consider vulnerabilities in one of their components to be a Spring vulnerability. At least they do not release an updated version until the next scheduled patch version, not even in the paid version.

You can either wait and accept being vulnerable or update the component yourself and therefore run an unsupported and untested configuration. Doomed if you do, doomed if you don't.

[cm2187]

And now that everything is a package, it won’t get fixed with windows update. Which means that if the website isn’t actively developed and regularly deployed, it will remain vulnerable

[voxic11]

Actually this bug is in Microsoft.AspNetCore.App.Runtime which is an implict package that comes from the runtime. So simply updating your version of the dotnet should fix any vulnerable applications.

[lsbehe]

M$ offers system wide installations. Those don't seem to be updated automatically either but at least I don't have to deploy 6 servers now.