Suggest improvements form drops the CVSS 3.1 vector when an advisory has both 3.1 and 4.0
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- security
Research direction
Start by examining the “Suggest improvements for this vulnerability” form and the generated changes in pull request #9627 for advisory GHSA-984m-rj28-8c6x. Reproduce a range-only edit on an advisory containing both CVSS 3.1 and 4.0 vectors, then verify that the CVSS 3.1 vector remains in the submitted advisory.
Written by the indexing model from the issue text.
Description
I used the "Suggest improvements for this vulnerability" form on GHSA-984m-rj28-8c6x to change the range of one entry. I did not touch the severity. But the pull request #9627 also removes the CVSS_V3 entry and keeps only CVSS_V4. Here is the part of its diff.
"severity": [
- {
- "type": "CVSS_V3",
- "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N"
- },
{
"type": "CVSS_V4",
"score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N"
The advisory has both vectors. The form has a "Severity" select with "Assess severity using CVSS v4" and one "Vector string" field, so it can hold only one vector. When I submit the form, the other vector is lost.
I expect the form to keep the CVSS 3.1 vector when I do not edit the severity.
- Dominant language
- No language data
- Stars
- 2.5k
- Forks
- 772
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 48
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/advisory-database
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
github/advisory-database#9255 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github/advisory-database#9164 · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github/advisory-database#8994 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
github/advisory-database#8898 · 4 comments · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github/advisory-database#8841 ·
All issues in github/advisory-database
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
punkpeye/mcp-remote#369 ·
-
Mend: dependency security vulnerability untriaged
Difficulty 1/5 Under an hour Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
cisagov/vulnrichment#337 ·
-
bug DUP Reservations
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
bcgov/reserve-rec-public#896 ·