-
Notifications
You must be signed in to change notification settings - Fork 32
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
Add VDT IT support: updated vulnerable package not reported as solved #4389
Conversation
..._detector/test_scan_results/data/test_cases/cases_scan_updated_package_still_vulnerable.yaml
Outdated
Show resolved
Hide resolved
...vulnerability_detector/data/feeds/canonical/custom_feed_updated_packace_still_vulnerable.xml
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great Job! 👏🏻
🗒️ Only a few changes are required.
..._detector/test_scan_results/data/test_cases/cases_scan_updated_package_still_vulnerable.yaml
Outdated
Show resolved
Hide resolved
..._detector/test_scan_results/data/test_cases/cases_scan_updated_package_still_vulnerable.yaml
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! 🚀
LGTM! |
This development has already been merged into Master, new target. So no new PR needed. Merged in ea84bee |
Description
This Issue aims to add IT support to verify when a package is vulnerable to a CVE and updated to a version that is still vulnerable, there is no alert showing the vulnerability as solved
Added
test_scan_updated_package_still_vulnerable.py
Testing performed