You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To make the Severity unique by combining the data source and CVE by putting the VendorSeverity of the Trivy scan result into the Severity of the cveContents.
CVSS of Trivy's scan results to be put into cvss3Vector and cvss3Score of the execution results of trivy-to-vuls.
In the current implementation of trivy-to-vuls, the type of data source that contributed to the determination of Severity is not considered, and the data source of cveContents' Cvss3Severity is treated as trivy. This means that if the same CVE is detected in different scan targets, it is impossible to distinguish whether the change in Severity is due to the difference in data sources or the change in Severity of the data source itself.
And We need to use the CVSS information from Trivy's scan results in FutureVuls.
Therefore, instead of lumping the data source into trivy, it is necessary to manage the Cvss3Severity of cveContents for each data source. By doing so, the value of Cvss3Severity, which is determined by the combination of data source and CVE, should be unique.
Remarks
The scan results of Trivy
In Trivy, when the same CVE is detected for different scan targets (in this case, assuming debian and ubuntu), the data source that contributes to the determination of Severity may differ depending on the scan target, which means that the same CVE can have different Severities.
Feature Request
In the current implementation of trivy-to-vuls, the type of data source that contributed to the determination of Severity is not considered, and the data source of cveContents' Cvss3Severity is treated as trivy. This means that if the same CVE is detected in different scan targets, it is impossible to distinguish whether the change in Severity is due to the difference in data sources or the change in Severity of the data source itself.
And We need to use the CVSS information from Trivy's scan results in FutureVuls.
The execution result of trivy-to-vuls
image debian:12
trivy -q image -f=json debian:12 | trivy-to-vuls parse --stdin
image ubuntu:22.04
trivy -q image -f=json ubuntu:22.04 | trivy-to-vuls parse --stdin
Therefore, instead of lumping the data source into
trivy
, it is necessary to manage the Cvss3Severity of cveContents for each data source. By doing so, the value of Cvss3Severity, which is determined by the combination of data source and CVE, should be unique.Remarks
The scan results of Trivy
In Trivy, when the same CVE is detected for different scan targets (in this case, assuming debian and ubuntu), the data source that contributes to the determination of Severity may differ depending on the scan target, which means that the same CVE can have different Severities.
image debian:12
image ubuntu:22.04
The decision logic of Severity in Trivy
The text was updated successfully, but these errors were encountered: