DependencyTrack / dependency-track

Dependency-Track is an intelligent Component Analysis platform that allows organizations to identify and reduce risk in the software supply chain.
https://dependencytrack.org/
Apache License 2.0
2.48k stars 536 forks source link

Add VEX Support for ' Action Statement' in Dependcy Track #3250

Open surendrapathak opened 8 months ago

surendrapathak commented 8 months ago

Current Behavior

As per "VEX" Min Spec

For status "affected", a VEX statement MUST include one [action_statement] that SHOULD describe actions to remediate or mitigate [vul_id].

The logical map for Action Statement is vulnerability->recommendation

Recommendations of how the vulnerability can be remediated or mitigated.

Within DependencyTrack, setting Analysis to "Exploitable" does not allow specifying a separate "Action Statement". A logical fallback is "Details". However, details maps to analysis->detail and not to vulnerability->recommendation.

Proposed Behavior

For state 'exploitable', introducing/re-purposing a text box for providing Action Statement that maps to vulnerability->recommendation in the specification

Checklist

nscuro commented 8 months ago

Thanks for raising this @surendrapathak!

Looking at the spec, the justification node is an enum, for which the predefined values only make sense when the analysis state is "not-affected": https://cyclonedx.org/docs/1.5/json/#vulnerabilities_items_analysis_justification

Did you mean to write vulnerability.recommendation instead perhaps?

surendrapathak commented 8 months ago

Ohh, sorry about that.. That's exactly what I meant. thanks for reading my mind :) Description updated to reflect recommendation instead of justification