Skip to content
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

x/vulndb: potential Go vuln in github.com/nghttp2/nghttp2: CVE-2020-11080 #2268

Closed
tatianab opened this issue Nov 8, 2023 · 1 comment
Closed
Labels
excluded: LEGACY_FALSE_POSITIVE (DO NOT USE) Vulnerability marked as false positive before we introduced the triage process

Comments

@tatianab
Copy link
Contributor

tatianab commented Nov 8, 2023

CVE-2020-11080 references github.com/nghttp2/nghttp2, which may be a Go module.

Description:
In nghttp2 before version 1.41.0, the overly large HTTP/2 SETTINGS frame payload causes denial of service. The proof of concept attack involves a malicious client constructing a SETTINGS frame with a length of 14,400 bytes (2400 individual settings entries) over and over again. The attack causes the CPU to spike at 100%. nghttp2 v1.41.0 fixes this vulnerability. There is a workaround to this vulnerability. Implement nghttp2_on_frame_recv_callback callback, and if received frame is SETTINGS frame and the number of settings entries are large (e.g., > 32), then drop the connection.

References:

Cross references:

See doc/triage.md for instructions on how to triage this report.

modules:
    - module: github.com/nghttp2/nghttp2
      vulnerable_at: 1.58.0
      packages:
        - package: nghttp2
cves:
    - CVE-2020-11080
references:
    - web: https://www.debian.org/security/2020/dsa-4696
    - web: http://lists.opensuse.org/opensuse-security-announce/2020-06/msg00024.html
    - web: https://lists.fedoraproject.org/archives/list/[email protected]/message/AAC2AA36OTRHKSVM5OV7TTVB3CZIGEFL/
    - web: https://www.oracle.com/security-alerts/cpujul2020.html
    - advisory: https://github.com/nghttp2/nghttp2/security/advisories/GHSA-q5wr-xfw9-q7xr
    - fix: https://github.com/nghttp2/nghttp2/commit/336a98feb0d56b9ac54e12736b18785c27f75090
    - fix: https://github.com/nghttp2/nghttp2/commit/f8da73bd042f810f34d19f9eae02b46d870af394
    - web: https://www.oracle.com/security-alerts/cpuoct2020.html
    - web: https://lists.fedoraproject.org/archives/list/[email protected]/message/4OOYAMJVLLCLXDTHW3V5UXNULZBBK4O6/
    - web: https://www.oracle.com/security-alerts/cpujan2021.html
    - web: https://www.oracle.com//security-alerts/cpujul2021.html
    - web: https://lists.debian.org/debian-lts-announce/2021/10/msg00011.html
    - web: https://www.oracle.com/security-alerts/cpuapr2022.html
    - web: https://lists.debian.org/debian-lts-announce/2023/10/msg00023.html

@tatianab tatianab added the excluded: LEGACY_FALSE_POSITIVE (DO NOT USE) Vulnerability marked as false positive before we introduced the triage process label Nov 8, 2023
@gopherbot
Copy link
Contributor

Change https://go.dev/cl/540721 mentions this issue: data/excluded: batch add 135 excluded reports

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
excluded: LEGACY_FALSE_POSITIVE (DO NOT USE) Vulnerability marked as false positive before we introduced the triage process
Projects
None yet
Development

No branches or pull requests

2 participants