Skip to content

Conversation

@valentijnscholten
Copy link
Member

Description

This PR fixes issue #12442 where importing BlackDuck Binary Analysis CSV reports does not populate the vulnerability_id field, even though vuln_id_from_tool is correctly set with the CVE.

Changes

  • Added unsaved_vulnerability_ids assignment when CVE is present in the finding
  • This ensures the vulnerability_id field is populated for de-duplication purposes
  • Follows the same pattern used in other parsers (e.g., dependency_check, openreports, auditjs)

Testing

  • Tested with the existing scan test files in unittests/scans/blackduck_binary_analysis/
  • The vulnerability_id field is now populated with the CVE value

Fixes #12442

- Add exception handling around CPE parsing in TenableCSVParser
- Log unsupported CPE versions at DEBUG level instead of crashing
- Allows import to continue when encountering unsupported CPE formats
- Fixes issue DefectDojo#11243
- Add unsaved_vulnerability_ids assignment when CVE is present
- This ensures the vulnerability_id field is populated for de-duplication
- Fixes DefectDojo#12442
…nalysis parser tests

- Verify unsaved_vulnerability_ids is populated with CVE value
- Add specific assertion for single vuln test case
- Add general assertion for multiple vulns test case
- Related to DefectDojo#12442
@valentijnscholten valentijnscholten added this to the 2.53.5 milestone Dec 23, 2025
Copy link
Contributor

@mtesauro mtesauro left a comment

Choose a reason for hiding this comment

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

Approved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Importing Blackduck Binary Analysis reports does not populate the Vulnerability Id field

3 participants