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

Support C/C++ #82

Open
oliverchang opened this issue Dec 19, 2022 · 6 comments
Open

Support C/C++ #82

oliverchang opened this issue Dec 19, 2022 · 6 comments
Labels
enhancement New feature or request

Comments

@oliverchang
Copy link
Collaborator

Connect osv-scanner with

  1. Build API for identifying vendored code osv.dev#561
  2. The OSV database contains 100% of vulnerabilities from NVD/CVE since 2016 that are determined to relate to OSS osv.dev#783

To provide C/C++ dependency detection and vuln management.

@oliverchang oliverchang added the enhancement New feature or request label Dec 19, 2022
@oliverchang
Copy link
Collaborator Author

@andrewpollock this would be the logical next step after your work on the NVD coverage!

@Chronial
Copy link

Chronial commented Dec 20, 2022

I don't know if this is the right place for this input. If not, please direct me somewhere else :).

The point of osv.dev#561 seems to be:

Given: file hashes
Return: Repository URL, CPEs, Closest tag/version

For our use case, the input of file hashes would be rather cumbersome. We know our dependencies and their versions – the main problem is effectively mapping these to CPEs. Since the input is not a package repository, but simply official releases / tags, there is no clear global identifier for the library.

Having an API that takes the library name or source repository URL as input and returns a CPE would be really helpful – or does this already exist?

@andrewpollock
Copy link
Contributor

Hi @Chronial,

Not at the API stage yet (or currently planned, but let's talk more). I've done some preliminary CPE Dictionary parsing looking for potential OSS repositories. Check out https://github.com/google/osv.dev/tree/master/vulnfeeds/cmd/cperepos#readme for what exists today. That's essentially CPE -> repository. There's nothing stopping that being reversed...

If you can elaborate a bit more on your use case, as my work on importing relevant CVEs from the NVD evolves, we can determine the appropriateness of turning this into an API.

@varun-endor
Copy link

@andrewpollock any rough ETA for C/C++ support? Thanks much for working on this btw.

@andrewpollock
Copy link
Contributor

@varun-endor it's an end-of-year goal overall, but per google/osv.dev#783 (comment) I'll break this down into some milestones for interested parties to follow along on.

@oliverchang
Copy link
Collaborator Author

The NVD database part is out now!

The remaining bits for OSV-Scanner support are:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants