Skip to content
New issue

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

Question: How to scan against the GIT ecosystem? #1352

Closed
landesfeind opened this issue Oct 29, 2024 · 1 comment
Closed

Question: How to scan against the GIT ecosystem? #1352

landesfeind opened this issue Oct 29, 2024 · 1 comment

Comments

@landesfeind
Copy link

landesfeind commented Oct 29, 2024

The OSV.dev database contains CVEs published through Github advisories in the Git ecosystem. When trying to scan dependencies of a project in this ecosystem, the scanning fails with { "code": 3, "message": "Invalid ecosystem" }.

Is this because of "GIT" not being a well-supported ecosystem by definition of the Open Source Vulnerability format? Is there a way to mitigate this?

Minimal working example

osv-scanner --lockfile=osv-scanner:mwe.json

where mwe.json contains

{ 
  "results": [
    {
      "packages": [
        {
          "package": {
            "ecosystem": "GIT",
            "name": "github.com/typo3/typo3",
            "version": "v10.0.0"
          }
        }
      ]
    }
  ]
}

This should result in the reporting of (at least) CVE-2024-34537.

$ osv-scanner --version
osv-scanner version: 1.9.0
commit: 1386406b64edd4544696183f273139ef9298f5df
built at: 2024-10-02T05:22:27Z

For completeness, using purl instead does not solve the problem because then the package is filtered out as a "local" package. Here is the mwe for that:

{ 
  "results": [
    {
      "packages": [
        {
          "package": {
            "purl": "pkg:github/typo3/typo3@v10.0.0"
          }
        }
      ]
    }
  ]
}
@landesfeind landesfeind changed the title How to scan against the GIT ecosystem? Question: How to scan against the GIT ecosystem? Oct 29, 2024
@landesfeind
Copy link
Author

I think it is related to this discussion in the osv.dev repo and I will follow up there.

@landesfeind landesfeind closed this as not planned Won't fix, can't repro, duplicate, stale Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant