Skip to content

fix: improve openjpeg checker #2526

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

Merged
merged 1 commit into from
Jan 25, 2023
Merged

Conversation

ffontaine
Copy link
Contributor

uclouvain:openjpeg is a valid CPE ID (and actually the only one with associated CVEs)

While at it, also add a debian test package and detect version 2 of openjpeg

Signed-off-by: Fabrice Fontaine [email protected]

uclouvain:openjpeg is a valid CPE ID (and actually the only one with associated
CVEs)

While at it, also add a debian test package and detect version 2 of
openjpeg

Signed-off-by: Fabrice Fontaine <[email protected]>
@ffontaine ffontaine force-pushed the fix-openjpeg-checker branch from 9f5f577 to 519c447 Compare January 24, 2023 10:07
Copy link
Contributor

@terriko terriko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! I wonder if we should suggest to NVD that the un-used one get removed? Do they even do that?

@terriko terriko merged commit daf57f5 into intel:main Jan 25, 2023
@ffontaine
Copy link
Contributor Author

NVD database has already been updated: https://nvd.nist.gov/products/cpe/search/results?namingFormat=2.3&keyword=cpe%3A2.3%3Aa%3Aopenjpeg%3Aopenjpeg.

However, cvedetails is keeping track of all those deprecated/old CPE IDs: https://www.cvedetails.com/product-search.php?vendor_id=0&search=openjpeg

@ffontaine ffontaine deleted the fix-openjpeg-checker branch January 25, 2023 08:00
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 this pull request may close these issues.

2 participants