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

Products are mainly associated with a vulnerabilty and not vulnerable #184

Open
Steppenw01f opened this issue Mar 6, 2022 · 0 comments · May be fixed by #271
Open

Products are mainly associated with a vulnerabilty and not vulnerable #184

Steppenw01f opened this issue Mar 6, 2022 · 0 comments · May be fixed by #271
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@Steppenw01f
Copy link

Steppenw01f commented Mar 6, 2022

The products and vendors, which are listed in the affected Column of a CVE are often not vulnerable.
For example:
The CVE-2021-44738 has multiple configurations, but only one of each configuration is vulnerable.
From the first configuration only "b2236_firmware" is vulnerable, but not "b2236", if you check the JSON object.
Screenshot 2022-03-06 013750

The solution would be to change the function convert_cve in opencve/utils.py.
Instead of just using the nested_lookup for the cpe23Uri, there could be a if-statement, checking if the boolean for vulnerable is True.

If there is a intend, that, for example the OS or the hardware is listed as affected in a CVE, then there could be another possibility to differentiate between associated and vulnerable products. The problem without distinction is, that, via the mail-service, the users gets a lot of notifications, which are not relevant, if he/she doesn't have the actual vulnerable software installed.

PS. big fan of this project, keep the good work up 😄

@ncrocfer ncrocfer added enhancement New feature or request good first issue Good for newcomers labels Mar 7, 2022
@Steppenw01f Steppenw01f linked a pull request Mar 13, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants