VulnerabilityDetailsResponse

data class VulnerabilityDetailsResponse(val cvssScore: Double, val cvssV2: CVSSResponse, val cvssV3: CVSSResponse, val cvssVersion: String, val effectiveSeverity: String, val packageIssue: List<PackageIssueResponse>, val severity: String, val type: String, val vexAssessment: VexAssessmentResponse)

Used by Occurrence to point to where the vulnerability exists and how to fix it.

Constructors

Link copied to clipboard
fun VulnerabilityDetailsResponse(cvssScore: Double, cvssV2: CVSSResponse, cvssV3: CVSSResponse, cvssVersion: String, effectiveSeverity: String, packageIssue: List<PackageIssueResponse>, severity: String, type: String, vexAssessment: VexAssessmentResponse)

Types

Link copied to clipboard
object Companion

Properties

Link copied to clipboard

The CVSS score of this vulnerability. CVSS score is on a scale of 0-10 where 0 indicates low severity and 10 indicates high severity.

Link copied to clipboard

The CVSS v2 score of this vulnerability.

Link copied to clipboard

The CVSS v3 score of this vulnerability.

Link copied to clipboard

CVSS version used to populate cvss_score and severity.

Link copied to clipboard

The distro assigned severity for this vulnerability when that is available and note provider assigned severity when distro has not yet assigned a severity for this vulnerability. When there are multiple package issues for this vulnerability, they can have different effective severities because some might come from the distro and some might come from installed language packs (e.g. Maven JARs or Go binaries). For this reason, it is advised to use the effective severity on the PackageIssue level, as this field may eventually be deprecated. In the case where multiple PackageIssues have different effective severities, the one set here will be the highest severity of any of the PackageIssues.

Link copied to clipboard

The set of affected locations and their fixes (if available) within the associated resource.

Link copied to clipboard

The note provider assigned Severity of the vulnerability.

Link copied to clipboard

The type of package; whether native or non native(ruby gems, node.js packages etc). This may be deprecated in the future because we can have multiple PackageIssues with different package types.

Link copied to clipboard

VexAssessment provides all publisher provided Vex information that is related to this vulnerability for this resource.