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

fix: improve validation of CPE data #4013

Closed
terriko opened this issue Apr 8, 2024 · 1 comment · Fixed by #4014
Closed

fix: improve validation of CPE data #4013

terriko opened this issue Apr 8, 2024 · 1 comment · Fixed by #4014

Comments

@terriko
Copy link
Contributor

terriko commented Apr 8, 2024

In #3990, @cinix has added the ability to read CPE info from CycloneDX triage data.

Some of the functions could use some additional input validation to make sure that the cpe conforms to expected format and that things like vendor/product/version don't have special characters in them. I expect for the moment we may see people using a lot of manually-edited triage files and typos are going to be more of a problem than malicious vex files, but we should treat it as untrusted data just in case. I expect a lot of the validation will look like the code we use in the PURL stuff that's been done recently; we might want to consider refactoring to re-use functions eventually.

@mastersans
Copy link
Member

I'll like to work on this one.

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

Successfully merging a pull request may close this issue.

2 participants