Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    ProGet: Vulnerability scanning of Chocolatey feeds

    Scheduled Pinned Locked Moved Support
    2 Posts 2 Posters 9 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A Offline
      am.infrastruktur_3111
      last edited by

      Are Chocolatey feeds included in the vulnerability scanning in the new ProGet 2024 (currently running 2024.2)?

      I pulled a sample package (.NET Core 8.0.1, package name 'dotnet'). This has some CVEs listed against it (e.g. https://www.cve.org/CVERecord?id=CVE-2024-21392), but ProGet shows 'None' under vulnerabilities.

      Is this the intended behaviour or am I missing something in my configuration for this to work?

      atrippA 1 Reply Last reply Reply Quote 0
      • atrippA Offline
        atripp inedo-engineer @am.infrastruktur_3111
        last edited by

        Hi @am-infrastruktur_3111 ,

        Chocolatey packages are scanned for viruses, so you will see those pop up. For example, pathdebug 0.3.4 should show up in ProGet's vulnerability system:
        https://security.inedo.com/vulnerability/details/PGV-2420934

        Otherwise, there is unfortunately no standardized/consistent naming for Windows software (unlike APK, APT, RPM, etc), so there's no way to associate a vulnerability report like CVE-2024-21392 with a software package.

        In this case, Microsoft calls the effected software ".NET 8.0", not .NET or dotnet, etc. In Other reports, they call it ".NET8", etc.

        And you can see that it translates a little weird n the CVE report as well:
        https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-21392

        ".NET 8.0 affected from 1.0.0 before 8.0.3 " - weird, right?

        This is a known issue in the industry for many years, and it would need to be address by Microsoft first. It's sadly not on their priority list.

        Best,
        Alana

        1 Reply Last reply Reply Quote 0

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better 💗

        Register Login
        • 1 / 1
        • First post
          Last post
        Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation