aboutcode-org / aboutcode-org/vulnerablecode

Decide what info we need to store on a grouped advisory

未關閉
#2,341 0 則留言 0 個 reaction 已指派 2 人 已被 @TG1999 認領 在 GitHub 檢視
主要語言
Python
星號
702
分支
328
平均合併
3 天 8 小時
30 天內合併 PR
3

描述

A grouped advisory is a group of multiple advisories which share common identifiers and have same packages in their affected and fixing ranges.

We need to decide what all information shall be stored on a grouped advisory and how it shall be calculated

Current info we store/show
- identifier - AVID of primary advisory
- aliases - aliases of all advisories
- risk_score - min(exploitability * weighted_severity, 10.0)
- weighted_severity - max severity of an advisory
- exploitability - max exploitability of an advisory
- summary - summary only of primary advisory
- ssvc_tress - all SSVC trees
- fixed_by_packages - they are already same for all advisories

TBD
- references
- weaknesses
- severities

We need to define this

貢獻指南

這個儲存庫沒有索引到貢獻指南

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。