We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As mentioned at https://x.com/stevegilham1/status/1817230285886324855, some things in FAKE are referencing versions of System.Formats.Asn1 with known security vulnerabilities.
I get this with the current master branch:
NuGet System.Formats.Asn1 - 7.0 is a transitive dependency. It is part of following dependency chains: -> Microsoft.Build.Tasks.Core - 17.0 -> System.Security.Cryptography.Pkcs - 7.0.3 -> System.Formats.Asn1 - 7.0 -> Microsoft.SqlServer.SqlManagementObjects - 161.46521.71 -> Microsoft.Data.SqlClient - 4.0 -> Microsoft.IdentityModel.JsonWebTokens - 6.15 -> Microsoft.IdentityModel.Tokens - 6.15 -> System.Security.Cryptography.Cng - 5.0 -> System.Formats.Asn1 - 7.0 -> NuGet.Protocol - 6.10.1 -> NuGet.Packaging - 6.10.1 -> System.Security.Cryptography.Pkcs - 7.0.3 -> System.Formats.Asn1 - 7.0 -> Paket.Core - 8.1.0-alpha004 -> NuGet.Packaging - 6.10.1 -> System.Security.Cryptography.Pkcs - 7.0.3 -> System.Formats.Asn1 - 7.0
And version 7.0 is listed on nuget.org as suffering from GHSA-447r-wph3-92pm.
Looks like the dependency needs updating to version 8.0.1 to fix the warning.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
As mentioned at https://x.com/stevegilham1/status/1817230285886324855, some things in FAKE are referencing versions of System.Formats.Asn1 with known security vulnerabilities.
I get this with the current master branch:
And version 7.0 is listed on nuget.org as suffering from GHSA-447r-wph3-92pm.
Looks like the dependency needs updating to version 8.0.1 to fix the warning.
The text was updated successfully, but these errors were encountered: