🐛 fix tenable #11102

[manuel-sommer]

#11102

[dryrunsecurity]

DryRun Security Summary

The pull request focuses on improving the functionality and accuracy of the Tenable CSV report parser, including adding a new test case to verify the parsing of a Tenable scan report for a specific issue related to the use of medium-strength SSL/TLS cipher suites, updating the get_findings function to handle the parsing of the "Steps to Remediate" field and improve the logic for converting severity values, and potential improvements to the handling of CVE and CPE values associated with the findings.

Expand for full summary

Summary:

The code changes in this pull request are focused on improving the functionality and accuracy of the Tenable CSV report parser, which is an important component of the application security toolchain. The changes include:

1. Adding a new test case to verify the parsing of a Tenable scan report for a specific issue (issue Tenable report field name change #11102) related to the use of medium-strength SSL/TLS cipher suites. This is a security-relevant finding, as the use of medium-strength ciphers can potentially lead to cryptographic attacks or brute-force attacks.

2. Updating the get_findings function in the TenableCSVParser class to handle the parsing of the "Steps to Remediate" field for findings, and improving the logic for converting severity values.

3. Potential improvements to the handling of CVE and CPE values associated with the findings, to ensure the extracted information is accurate and reliable.

Overall, the changes appear to be focused on enhancing the security-related functionality of the Tenable CSV report parser, which is a positive step from an application security perspective.

Files Changed:

1. unittests/tools/test_tenable_parser.py: This file has been updated to include a new test case, test_parse_issue_11102, which verifies the parsing of a Tenable scan report for a specific issue related to the use of medium-strength SSL/TLS cipher suites.

2. unittests/scans/tenable/issue_11102.csv: This file contains the Tenable scan report data for the issue Tenable report field name change #11102, which is used in the new test case.

3. dojo/tools/tenable/csv_format.py: This file has been updated to improve the handling of the "Steps to Remediate" field and the severity conversion logic in the TenableCSVParser class.

Code Analysis

We ran 9 analyzers against 3 files and 0 analyzers had findings. 9 analyzers had no findings.

Riskiness

🟢 Risk threshold not exceeded.

View PR in the DryRun Dashboard.

[mtesauro]

Approved