feat(manifest): socket manifest dotnet + centralized config-name globs (REA-627, REA-628) by jfblaa · Pull Request #1404 · SocketDev/socket-cli

Pull Request #1404 Alerts: Complete with warnings

Report	Status	Message
PR #1404 Alerts	⚠️	Found 1 project alert

Pull request alerts notify when new issues are detected between the diff of the pull request and it's target branch.

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert (click "▶" to expand/collapse)
Warn		Critical CVE: NuGet Client Security Feature Bypass Vulnerability in nuget `nuget.packaging` CVE: GHSA-68w7-72jg-6qpp NuGet Client Security Feature Bypass Vulnerability (CRITICAL) Affected versions: = 6.7.0, 6.8.0; >= 4.6.0 < 5.11.6; >= 6.0.0 < 6.0.6; >= 6.3.0 < 6.3.4; >= 6.4.0 < 6.4.3; >= 6.6.0 < 6.6.2; >= 6.7.0 < 6.7.1; >= 6.8.0 < 6.8.1 Patched version: 6.0.6 From: src/commands/manifest/scripts/dotnet-tool/socket-facts-dotnet.csproj → `nuget/nuget.packaging@6.0.0` ℹ Read more on: This package \| This alert \| What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore nuget/nuget.packaging@6.0.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.