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

Split different products of a single cve-number to different database entrys #71

Closed
KnYL3R opened this issue Jun 12, 2024 · 1 comment
Closed

Comments

@KnYL3R
Copy link
Collaborator

KnYL3R commented Jun 12, 2024

Sadly one CVE-number can be used to track multiple products.
That is why is it necessary to separate them.

@KnYL3R
Copy link
Collaborator Author

KnYL3R commented Jun 12, 2024

CVE-2022-27194

@KnYL3R KnYL3R pinned this issue Jun 12, 2024
@KnYL3R KnYL3R closed this as completed Nov 6, 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