Skip to content

[Epic] NuGet Package Vulnerability Auditing #8087

Open

Description

@anangaur

The NuGet team is following a know, prevent, fix framework to be proactive and take preventive measures to avoid security problems such as known vulnerabilities. This can be described as the following:

  1. Know about the vulnerabilities in your software
  2. Prevent the addition of new vulnerabilities
  3. Fix or remove vulnerabilities.

The following work below represents each of these categories.

Know your vulnerabilities 👀

Prevent new vulnerabilities ⚠️

Fix or remove vulnerabilities 🔧

Please 👍 or 👎 this comment to help us with the direction of this epic & leave as much feedback/questions/concerns as you'd like on this issue itself and we will get back to you shortly.

Further tracking issues will be created shortly as requirements are gathered and planned.

Activity

  1. self-assigned this
    on Aug 15, 2019
  2. changed the title [-][Security] Flag vulnerable packages[/-] [+]Flag vulnerable packages[/+] on Aug 15, 2019
  3. pascalberger commented on Oct 29, 2019

    @pascalberger

    Are there plans to support writing the output of dotnet list --vulnerable into a machine readable file? This would allow to use this command in scenarios like during a CI build, to block introducing packages with known vulnerabilities.

  4. pascalberger commented on Oct 29, 2019

    @pascalberger

    Who are the customers
    All .NET Core customers.

    Why are only .NET Core customers the target audience for this? Are there any technical restrictions why it does not work for .NET Framework projects? Will it be only PackageReference or also packages.config projects?

  5. anangaur commented on Oct 29, 2019

    @anangaur
    Author

    Great questions @pascalberger. We should be making this info available to nuget.exe or msbuild.exe or both. We did discuss this but looks like we failed to mention it in the spec. /cc: @xavierdecoster

  6. zkat commented on Oct 30, 2019

    @zkat
    Contributor

    My main concern with this spec as-is is that it focuses so much on the informational aspect. When designing npm audit, our hypothesis was that it was much more important to make sure customers had specific actions they could do right away. Being informational tends to risk something becoming just plain noise that they'll tune out, and it doesn't result in people driving towards a more secure ecosystem. What's the expected workflow for people being able to pick non-vulnerable packages, once they're informed? For example, I wrote npm audit fix and it was available immediately after initial launch.

  7. anangaur commented on Oct 30, 2019

    @anangaur
    Author

    @zkat This is definitely on the cards as part of Stage 2 where we plan to implement an audit or equivalent command. Thanks for bringing this up! I have added a line in the spec to indicate we do want to have a way to fix as well.

  8. anangaur commented on Jun 2, 2020

    @anangaur
    Author

    @skofman1 This should be the epic issue that should link any intermediate issues tracking the feature. Can you help me in linking the in-progress and planed items here from https://github.com/NuGet/nugetgallery/ or anywhere else?

  9. 22 remaining items

  10. changed the title [-]Package Vulnerability Audit (PVA)[/-] [+]Package Vulnerability Audit (PVA) Epic[/+] on Jan 31, 2023
  11. kapsiR commented on Mar 2, 2023

    @kapsiR

    Since the planned package audit features are going in the right direction 👏👍, are there any plans to actively help putting vulnerability information into the system? (server side)

    One pretty famous example in my opinion is the recent event with a very outdated curl package:
    https://daniel.haxx.se/blog/2023/03/02/the-curl-nuget-story/

  12. JonDouglas commented on Mar 20, 2023

    @JonDouglas
    Contributor

    @kapsiR This is a very complex topic. I hope to write a blog shortly talking about some of the challenges here.

    NuGet is an intermediate. We use a centralized supplier known as the CVE (list of publicly disclosed vulnerabilities) through GitHub Advisories. For libraries like Curl, they maintain a thorough list of CVEs.

    As you may imagine, the challenge here happens when a package derives another and whether it is actually maintained or not. NuGet being an intermediate, we do not issue CVEs. We rely on a CNA(CVE Numbering Authority) to do so on behalf of the reporter and the maintainer of a package who becomes aware of a vulnerability.

    When we become aware of any vulnerability, we tend to bridge the connection of the reporter and the maintainer to take action and our due diligence on behalf of the community.

    If you have ideas for how we can bridge this gap further, please do file another issue with more details. We rely on the effort of our maintainer ecosystem to stay current with known vulnerabilities and ensuring each CVE has high-quality data. If you suspect any other notable libraries and their NuGet derivatives may contain known vulnerabilities, please reach out to the maintainer and send us a support request so we can be aware of it if they are unresponsive.

  13. added this to the milestone on Mar 22, 2023
  14. changed the title [-]Package Vulnerability Audit (PVA) Epic[/-] [+][Epic] NuGet Package Vulnerability Auditing[/+] on Mar 24, 2023
  15. self-assigned this
    on Apr 24, 2023
  16. modified the milestones: , 6.8 on Jun 29, 2023
  17. removed this from the 6.8 milestone on Oct 31, 2023
  18. JonDouglas commented on Nov 25, 2023

    @JonDouglas
    Contributor

    Hi folks,

    Much of this work was released with NuGet 6.8:

    https://devblogs.microsoft.com/nuget/announcing-nuget-6-8-maintaining-security-with-ease/

    We may need to re-organize this issue with our plans going into next year. You can also view our documentation for auditing experiences here:

    https://learn.microsoft.com/en-us/nuget/concepts/auditing-packages

    I will likely work with the team to create individual epics based on the new work areas we have started such as auditing at restore time, auditing affordances in tooling, and security enhancements made to NuGet gallery. Thus we may close this to better track work long term on an area basis. This epic might be too large right now to know what's actually happening.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions