trivy: map status field#12686
Conversation
|
This pull request contains a unit test JSON file with sensitive configuration details, but since it is located in a test directory and not intended for production deployment, the information disclosure is considered low risk and non-blocking.
Information Disclosure in
|
| Vulnerability | Information Disclosure |
|---|---|
| Description | The unit test JSON file contains detailed system configuration and vulnerability information. However, this is a unit test file typically not deployed in production and used for testing purposes. While the file contains sensitive information, its presence in a test directory does not constitute a significant security risk, especially for unit testing scenarios. |
django-DefectDojo/unittests/scans/trivy/all_statuses.json
Lines 1 to 603 in 5c03fa8
All finding details can be found in the DryRun Security Dashboard.
|
I agree with most of these except where |
adjusted |
Trivy has a "status" field for triaging which is currently unmapped:
"status": "affected" or "not_affected" or "fix_deferred" or "will_not_fix"
This would be useful information to handle.
see: https://trivy.dev/latest/docs/configuration/filtering/
"Affected": the package is affected by the flaw on this platform
"Not affected": the package, which ships on this platform, is not affected by the flaw
"Fix deferred": the package is affected by the flaw on this platform, and may be fixed in the future
"Under investigation": it is currently unknown whether the flaw affects the package on this platform, and is under investigation
"Will not fix": the package is affected by the flaw on this platform, but there is no current intention to fix it (primarily for flaws that are of Low or Moderate impact that pose no significant risk to customers)
This PR stores the Trivy
statusvalue in theImpactfield.It also tries to map the
statusto Defect Dojo status flags. This is not trivial as thestatusof the vulnerability in the Trivy report is set by the OS/Package vendor. If they statewill_not_fixit doesn't automatically mean Defect Dojo needs to close the finding on import.The
trivy.mdfile in this PR contains a table with status flag mappings.[sc-11484]