fkie_cve-2024-22189
Vulnerability from fkie_nvd
Published
2024-04-04 15:15
Modified
2024-11-21 08:55
Severity ?
7.5 (High) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Summary
quic-go is an implementation of the QUIC protocol in Go. Prior to version 0.42.0, an attacker can cause its peer to run out of memory sending a large number of `NEW_CONNECTION_ID` frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a `RETIRE_CONNECTION_ID` frame. The attacker can prevent the receiver from sending out (the vast majority of) these `RETIRE_CONNECTION_ID` frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate. Version 0.42.0 contains a patch for the issue. No known workarounds are available.
References
security-advisories@github.comhttps://github.com/quic-go/quic-go/commit/4a99b816ae3ab03ae5449d15aac45147c85ed47a
security-advisories@github.comhttps://github.com/quic-go/quic-go/security/advisories/GHSA-c33x-xqrf-c478
security-advisories@github.comhttps://seemann.io/posts/2024-03-19-exploiting-quics-connection-id-management
security-advisories@github.comhttps://www.youtube.com/watch?v=JqXtYcZAtIA&t=3683s
af854a3a-2127-422b-91ae-364da2661108https://github.com/quic-go/quic-go/commit/4a99b816ae3ab03ae5449d15aac45147c85ed47a
af854a3a-2127-422b-91ae-364da2661108https://github.com/quic-go/quic-go/security/advisories/GHSA-c33x-xqrf-c478
af854a3a-2127-422b-91ae-364da2661108https://seemann.io/posts/2024-03-19-exploiting-quics-connection-id-management
af854a3a-2127-422b-91ae-364da2661108https://www.youtube.com/watch?v=JqXtYcZAtIA&t=3683s
Impacted products
Vendor Product Version


To clipboard 

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "quic-go is an implementation of the QUIC protocol in Go. Prior to version 0.42.0, an attacker can cause its peer to run out of memory sending a large number of `NEW_CONNECTION_ID` frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a `RETIRE_CONNECTION_ID` frame. The attacker can prevent the receiver from sending out (the vast majority of) these `RETIRE_CONNECTION_ID` frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer\u0027s RTT estimate. Version 0.42.0 contains a patch for the issue. No known workarounds are available."
    },
    {
      "lang": "es",
      "value": "quic-go es una implementaci\u00f3n del protocolo QUIC en Go. Antes de la versi\u00f3n 0.42.0, un atacante pod\u00eda hacer que su par se quedara sin memoria enviando una gran cantidad de tramas `NEW_CONNECTION_ID` que retiraban los ID de conexi\u00f3n antiguos. Se supone que el receptor debe responder a cada cuadro de retiro con un cuadro `RETIRE_CONNECTION_ID`. El atacante puede evitar que el receptor env\u00ede (la gran mayor\u00eda de) estas tramas `RETIRE_CONNECTION_ID` colapsando la ventana de congesti\u00f3n del par (al reconocer selectivamente los paquetes recibidos) y manipulando la estimaci\u00f3n de RTT del par. La versi\u00f3n 0.42.0 contiene un parche para el problema. No hay workarounds disponibles."
    }
  ],
  "id": "CVE-2024-22189",
  "lastModified": "2024-11-21T08:55:45.517",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "HIGH",
          "baseScore": 7.5,
          "baseSeverity": "HIGH",
          "confidentialityImpact": "NONE",
          "integrityImpact": "NONE",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
          "version": "3.1"
        },
        "exploitabilityScore": 3.9,
        "impactScore": 3.6,
        "source": "security-advisories@github.com",
        "type": "Secondary"
      }
    ]
  },
  "published": "2024-04-04T15:15:37.990",
  "references": [
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/quic-go/quic-go/commit/4a99b816ae3ab03ae5449d15aac45147c85ed47a"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/quic-go/quic-go/security/advisories/GHSA-c33x-xqrf-c478"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://seemann.io/posts/2024-03-19-exploiting-quics-connection-id-management"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://www.youtube.com/watch?v=JqXtYcZAtIA\u0026t=3683s"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "url": "https://github.com/quic-go/quic-go/commit/4a99b816ae3ab03ae5449d15aac45147c85ed47a"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "url": "https://github.com/quic-go/quic-go/security/advisories/GHSA-c33x-xqrf-c478"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "url": "https://seemann.io/posts/2024-03-19-exploiting-quics-connection-id-management"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "url": "https://www.youtube.com/watch?v=JqXtYcZAtIA\u0026t=3683s"
    }
  ],
  "sourceIdentifier": "security-advisories@github.com",
  "vulnStatus": "Awaiting Analysis",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-770"
        }
      ],
      "source": "security-advisories@github.com",
      "type": "Secondary"
    }
  ]
}


Log in or create an account to share your comment.




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.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • 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.