Skip to content

Add optional CVSS vectors to vulnerability objects

Oscar Tovar requested to merge otovar/add-optional-cvss-vectors into master

What does this MR do?

This MR adds an optional cvss_vectors field to the vulnerability object. The field's object requires a vendor and a vector which help identify a valid CVSS score, and the vendor that assigned it (for example RedHat). To validate successfully, the optional field must have at least one item, and it must match a known CVSS pattern (either 2, 3.0, or 3.1).

What are the relevant issue numbers?

Closes gitlab-org/gitlab#422031 (closed)

Checklist

Merge request reports