-
Notifications
You must be signed in to change notification settings - Fork 540
[GHSA-mq3p-rrmp-79jg] go-ethereum is vulnerable to high CPU usage leading to DoS via malicious p2p message #7103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: timothyfraser1955-del/advisory-improvement-7103
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -1,7 +1,7 @@ | ||||||
| { | ||||||
| "schema_version": "1.4.0", | ||||||
| "id": "GHSA-mq3p-rrmp-79jg", | ||||||
| "modified": "2026-01-13T21:55:29Z", | ||||||
| "modified": "2026-01-13T22:15:33Z", | ||||||
| "published": "2026-01-13T21:55:29Z", | ||||||
| "aliases": [ | ||||||
| "CVE-2026-22868" | ||||||
|
|
@@ -11,7 +11,7 @@ | |||||
| "severity": [ | ||||||
| { | ||||||
| "type": "CVSS_V4", | ||||||
| "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N" | ||||||
| "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:N" | ||||||
| } | ||||||
| ], | ||||||
| "affected": [ | ||||||
|
|
@@ -61,7 +61,7 @@ | |||||
| "CWE-20", | ||||||
| "CWE-400" | ||||||
| ], | ||||||
| "severity": "HIGH", | ||||||
| "severity": "CRITICAL", | ||||||
|
||||||
| "severity": "CRITICAL", | |
| "severity": "HIGH", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The CVSS v4 vector sets confidentiality/integrity impacts (VC/VI) and subsequent system impacts (SC/SI) to High, but this advisory’s summary/details describe a CPU-exhaustion DoS. Unless there’s evidence of data compromise or downstream system impact, the vector should reflect availability-only impact (e.g., VC:N/VI:N with VA:H and typically SC/SI:N). Please re-check the CVSS v4 scoring source (GitHub/NVD) and update the vector accordingly.