fkie_cve-2024-45810
Vulnerability from fkie_nvd
Published
2024-09-20 00:15
Modified
2024-09-24 19:48
Summary
Envoy is a cloud-native high-performance edge/middle/service proxy. Envoy will crash when the http async client is handling `sendLocalReply` under some circumstance, e.g., websocket upgrade, and requests mirroring. The http async client will crash during the `sendLocalReply()` in http async client, one reason is http async client is duplicating the status code, another one is the destroy of router is called at the destructor of the async stream, while the stream is deferred deleted at first. There will be problems that the stream decoder is destroyed but its reference is called in `router.onDestroy()`, causing segment fault. This will impact ext_authz if the `upgrade` and `connection` header are allowed, and request mirrorring. This issue has been addressed in versions 1.31.2, 1.30.6, 1.29.9, and 1.28.7. Users are advised to upgrade. There are no known workarounds for this vulnerability.
Impacted products
Vendor Product Version
envoyproxy envoy *
envoyproxy envoy *
envoyproxy envoy *
envoyproxy envoy *



{
   configurations: [
      {
         nodes: [
            {
               cpeMatch: [
                  {
                     criteria: "cpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:*",
                     matchCriteriaId: "C5E423BE-4022-47AB-A5D4-B218627517DD",
                     versionEndExcluding: "1.28.7",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:*",
                     matchCriteriaId: "E442EF13-A99D-42B9-BC76-AC398C32D132",
                     versionEndExcluding: "1.29.9",
                     versionStartIncluding: "1.29.0",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:*",
                     matchCriteriaId: "D9685C62-CFE4-43C5-B0C2-1C6722FB4F64",
                     versionEndExcluding: "1.30.6",
                     versionStartIncluding: "1.30.0",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:*",
                     matchCriteriaId: "C765FFC0-2FF7-4318-A347-2AFCAD0E7C74",
                     versionEndExcluding: "1.31.2",
                     versionStartIncluding: "1.31.0",
                     vulnerable: true,
                  },
               ],
               negate: false,
               operator: "OR",
            },
         ],
      },
   ],
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "Envoy is a cloud-native high-performance edge/middle/service proxy. Envoy will crash when the http async client is handling `sendLocalReply` under some circumstance, e.g., websocket upgrade, and requests mirroring. The http async client will crash during the `sendLocalReply()` in http async client, one reason is http async client is duplicating the status code, another one is the destroy of router is called at the destructor of the async stream, while the stream is deferred deleted at first. There will be problems that the stream decoder is destroyed but its reference is called in `router.onDestroy()`, causing segment fault. This will impact ext_authz if the `upgrade` and `connection` header are allowed, and request mirrorring. This issue has been addressed in versions 1.31.2, 1.30.6, 1.29.9, and 1.28.7. Users are advised to upgrade. There are no known workarounds for this vulnerability.",
      },
      {
         lang: "es",
         value: "Envoy es un proxy de servicio/borde/medio de alto rendimiento nativo de la nube. Envoy se bloqueará cuando el cliente asincrónico http esté manejando `sendLocalReply` en alguna circunstancia, por ejemplo, actualización de websocket y duplicación de solicitudes. El cliente asincrónico http se bloqueará durante `sendLocalReply()` en el cliente asincrónico http, una razón es que el cliente asincrónico http está duplicando el código de estado, otra es que la destrucción del enrutador se llama en el destructor de la transmisión asincrónica, mientras que la transmisión se elimina diferida al principio. Habrá problemas si se destruye el decodificador de transmisión, pero se llama a su referencia en `router.onDestroy()`, lo que provoca una falla de segmento. Esto afectará a ext_authz si se permiten los encabezados `upgrade` y `connection`, y solicitará duplicación. Este problema se ha solucionado en las versiones 1.31.2, 1.30.6, 1.29.9 y 1.28.7. Se recomienda a los usuarios que actualicen. No se conocen workarounds para esta vulnerabilidad.",
      },
   ],
   id: "CVE-2024-45810",
   lastModified: "2024-09-24T19:48:22.993",
   metrics: {
      cvssMetricV31: [
         {
            cvssData: {
               attackComplexity: "LOW",
               attackVector: "NETWORK",
               availabilityImpact: "HIGH",
               baseScore: 6.5,
               baseSeverity: "MEDIUM",
               confidentialityImpact: "NONE",
               integrityImpact: "NONE",
               privilegesRequired: "LOW",
               scope: "UNCHANGED",
               userInteraction: "NONE",
               vectorString: "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
               version: "3.1",
            },
            exploitabilityScore: 2.8,
            impactScore: 3.6,
            source: "security-advisories@github.com",
            type: "Secondary",
         },
         {
            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: "nvd@nist.gov",
            type: "Primary",
         },
      ],
   },
   published: "2024-09-20T00:15:03.153",
   references: [
      {
         source: "security-advisories@github.com",
         tags: [
            "Exploit",
            "Third Party Advisory",
         ],
         url: "https://github.com/envoyproxy/envoy/security/advisories/GHSA-qm74-x36m-555q",
      },
   ],
   sourceIdentifier: "security-advisories@github.com",
   vulnStatus: "Analyzed",
   weaknesses: [
      {
         description: [
            {
               lang: "en",
               value: "CWE-119",
            },
         ],
         source: "security-advisories@github.com",
         type: "Secondary",
      },
      {
         description: [
            {
               lang: "en",
               value: "NVD-CWE-noinfo",
            },
         ],
         source: "nvd@nist.gov",
         type: "Primary",
      },
   ],
}


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.


Loading…

Loading…

Loading…

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.