gsd-2024-27983
Vulnerability from gsd
Modified
2024-02-29 06:03
Details
An attacker can make the Node.js HTTP/2 server completely unavailable by sending a small amount of HTTP/2 frames packets with a few HTTP/2 frames inside. It is possible to leave some data in nghttp2 memory after reset when headers with HTTP/2 CONTINUATION frame are sent to the server and then a TCP connection is abruptly closed by the client triggering the Http2Session destructor while header frames are still being processed (and stored in memory) causing a race condition.
Aliases


To clipboard 

{
   gsd: {
      metadata: {
         exploitCode: "unknown",
         remediation: "unknown",
         reportConfidence: "confirmed",
         type: "vulnerability",
      },
      osvSchema: {
         aliases: [
            "CVE-2024-27983",
         ],
         details: "An attacker can make the Node.js HTTP/2 server completely unavailable by sending a small amount of HTTP/2 frames packets with a few HTTP/2 frames inside. It is possible to leave some data in nghttp2 memory after reset when headers with HTTP/2 CONTINUATION frame are sent to the server and then a TCP connection is abruptly closed by the client triggering the Http2Session destructor while header frames are still being processed (and stored in memory) causing a race condition.",
         id: "GSD-2024-27983",
         modified: "2024-02-29T06:03:30.436288Z",
         schema_version: "1.4.0",
      },
   },
   namespaces: {
      "cve.org": {
         CVE_data_meta: {
            ASSIGNER: "support@hackerone.com",
            ID: "CVE-2024-27983",
            STATE: "PUBLIC",
         },
         affects: {
            vendor: {
               vendor_data: [
                  {
                     product: {
                        product_data: [
                           {
                              product_name: "Node",
                              version: {
                                 version_data: [
                                    {
                                       version_affected: "<=",
                                       version_name: "18.20.0",
                                       version_value: "18.20.0",
                                    },
                                    {
                                       version_affected: "<=",
                                       version_name: "20.12.0",
                                       version_value: "20.12.0",
                                    },
                                    {
                                       version_affected: "<=",
                                       version_name: "21.7.1",
                                       version_value: "21.7.1",
                                    },
                                 ],
                              },
                           },
                        ],
                     },
                     vendor_name: "Node.js",
                  },
               ],
            },
         },
         data_format: "MITRE",
         data_type: "CVE",
         data_version: "4.0",
         description: {
            description_data: [
               {
                  lang: "eng",
                  value: "An attacker can make the Node.js HTTP/2 server completely unavailable by sending a small amount of HTTP/2 frames packets with a few HTTP/2 frames inside. It is possible to leave some data in nghttp2 memory after reset when headers with HTTP/2 CONTINUATION frame are sent to the server and then a TCP connection is abruptly closed by the client triggering the Http2Session destructor while header frames are still being processed (and stored in memory) causing a race condition.",
               },
            ],
         },
         impact: {
            cvss: [
               {
                  baseScore: 8.2,
                  baseSeverity: "HIGH",
                  vectorString: "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H",
                  version: "3.0",
               },
            ],
         },
         problemtype: {
            problemtype_data: [
               {
                  description: [
                     {
                        lang: "eng",
                        value: "n/a",
                     },
                  ],
               },
            ],
         },
         references: {
            reference_data: [
               {
                  name: "https://hackerone.com/reports/2319584",
                  refsource: "MISC",
                  url: "https://hackerone.com/reports/2319584",
               },
               {
                  name: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JDECX4BYZLMM4S4LALN4DPZ2HUTTPLKE/",
                  refsource: "MISC",
                  url: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JDECX4BYZLMM4S4LALN4DPZ2HUTTPLKE/",
               },
               {
                  name: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YDVFUH7ACZPYB3BS4SVILNOY7NQU73VW/",
                  refsource: "MISC",
                  url: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YDVFUH7ACZPYB3BS4SVILNOY7NQU73VW/",
               },
            ],
         },
      },
      "nvd.nist.gov": {
         cve: {
            descriptions: [
               {
                  lang: "en",
                  value: "An attacker can make the Node.js HTTP/2 server completely unavailable by sending a small amount of HTTP/2 frames packets with a few HTTP/2 frames inside. It is possible to leave some data in nghttp2 memory after reset when headers with HTTP/2 CONTINUATION frame are sent to the server and then a TCP connection is abruptly closed by the client triggering the Http2Session destructor while header frames are still being processed (and stored in memory) causing a race condition.",
               },
               {
                  lang: "es",
                  value: "Un atacante puede hacer que el servidor HTTP/2 de Node.js no esté completamente disponible enviando una pequeña cantidad de paquetes de tramas HTTP/2 con algunas tramas HTTP/2 en su interior. Es posible dejar algunos datos en la memoria nghttp2 después del reinicio cuando los encabezados con el frame de CONTINUATION HTTP/2 se envían al servidor y luego el cliente cierra abruptamente una conexión TCP activando el destructor Http2Session mientras los frames de encabezado aún se están procesando (y almacenando en la memoria) causando una condición de ejecución.",
               },
            ],
            id: "CVE-2024-27983",
            lastModified: "2024-04-20T02:15:06.660",
            metrics: {
               cvssMetricV30: [
                  {
                     cvssData: {
                        attackComplexity: "LOW",
                        attackVector: "NETWORK",
                        availabilityImpact: "HIGH",
                        baseScore: 8.2,
                        baseSeverity: "HIGH",
                        confidentialityImpact: "NONE",
                        integrityImpact: "LOW",
                        privilegesRequired: "NONE",
                        scope: "UNCHANGED",
                        userInteraction: "NONE",
                        vectorString: "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H",
                        version: "3.0",
                     },
                     exploitabilityScore: 3.9,
                     impactScore: 4.2,
                     source: "support@hackerone.com",
                     type: "Secondary",
                  },
               ],
            },
            published: "2024-04-09T01:15:49.197",
            references: [
               {
                  source: "support@hackerone.com",
                  url: "https://hackerone.com/reports/2319584",
               },
               {
                  source: "support@hackerone.com",
                  url: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JDECX4BYZLMM4S4LALN4DPZ2HUTTPLKE/",
               },
               {
                  source: "support@hackerone.com",
                  url: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YDVFUH7ACZPYB3BS4SVILNOY7NQU73VW/",
               },
            ],
            sourceIdentifier: "support@hackerone.com",
            vulnStatus: "Awaiting Analysis",
         },
      },
   },
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.