CVE-2025-24030

{
  "id": "CVE-2025-24030",
  "cveTags": [],
  "metrics": {
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2025-24030",
          "role": "CISA Coordinator",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "no"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "version": "2.0.3",
          "timestamp": "2025-01-23T14:58:52.009540Z"
        }
      }
    ],
    "cvssMetricV31": [
      {
        "type": "Secondary",
        "source": "security-advisories@github.com",
        "cvssData": {
          "scope": "UNCHANGED",
          "version": "3.1",
          "baseScore": 7.1,
          "attackVector": "ADJACENT_NETWORK",
          "baseSeverity": "HIGH",
          "vectorString": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H",
          "integrityImpact": "NONE",
          "userInteraction": "NONE",
          "attackComplexity": "LOW",
          "availabilityImpact": "HIGH",
          "privilegesRequired": "NONE",
          "confidentialityImpact": "LOW"
        },
        "impactScore": 4.2,
        "exploitabilityScore": 2.8
      }
    ]
  },
  "affected": [
    {
      "source": "security-advisories@github.com",
      "affectedData": [
        {
          "vendor": "envoyproxy",
          "product": "gateway",
          "versions": [
            {
              "status": "affected",
              "version": "< 1.2.6"
            }
          ]
        }
      ]
    }
  ],
  "published": "2025-01-23T04:15:07.100",
  "references": [
    {
      "url": "https://github.com/envoyproxy/gateway/commit/3eb3301ab3dbf12b201b47bdb6074d1233be07bd",
      "tags": [
        "Patch"
      ],
      "source": "security-advisories@github.com"
    },
    {
      "url": "https://github.com/envoyproxy/gateway/security/advisories/GHSA-j777-63hf-hx76",
      "tags": [
        "Mitigation",
        "Third Party Advisory"
      ],
      "source": "security-advisories@github.com"
    },
    {
      "url": "https://www.envoyproxy.io/docs/envoy/latest/configuration/best_practices/edge",
      "tags": [
        "Product"
      ],
      "source": "security-advisories@github.com"
    },
    {
      "url": "https://www.envoyproxy.io/docs/envoy/latest/operations/admin",
      "tags": [
        "Product"
      ],
      "source": "security-advisories@github.com"
    }
  ],
  "vulnStatus": "Analyzed",
  "weaknesses": [
    {
      "type": "Secondary",
      "source": "security-advisories@github.com",
      "description": [
        {
          "lang": "en",
          "value": "CWE-419"
        }
      ]
    }
  ],
  "descriptions": [
    {
      "lang": "en",
      "value": "Envoy Gateway is an open source project for managing Envoy Proxy as a standalone or Kubernetes-based application gateway. A user with access to the Kubernetes cluster can use a path traversal attack to execute Envoy Admin interface commands on proxies managed by any version of Envoy Gateway prior to 1.2.6. The admin interface can be used to terminate the Envoy process and extract the Envoy configuration (possibly containing confidential data). Version 1.2.6 fixes the issue. As a workaround, the `EnvoyProxy` API can be used to apply a bootstrap config patch that restricts access strictly to the prometheus stats endpoint. Find below an example of such a bootstrap patch."
    },
    {
      "lang": "es",
      "value": "Envoy Gateway es un proyecto de código abierto para administrar Envoy Proxy como una puerta de enlace de aplicaciones independiente o basada en Kubernetes. Un usuario con acceso al clúster de Kubernetes puede usar un ataque de recorrido de ruta para ejecutar comandos de la interfaz de administración de Envoy en servidores proxy administrados por cualquier versión de Envoy Gateway anterior a la 1.2.6. La interfaz de administración se puede usar para finalizar el proceso de Envoy y extraer la configuración de Envoy (que posiblemente contenga datos confidenciales). La versión 1.2.6 soluciona el problema. Como workaround, se puede usar la API `EnvoyProxy` para aplicar un parche de configuración de arranque que restrinja el acceso estrictamente al endpoint de estadísticas de Prometheus. A continuación, encontrará un ejemplo de un parche de arranque de este tipo."
    }
  ],
  "lastModified": "2026-06-17T08:57:55.383",
  "configurations": [
    {
      "nodes": [
        {
          "negate": false,
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:envoyproxy:gateway:*:*:*:*:*:*:*:*",
              "vulnerable": true,
              "matchCriteriaId": "0526026F-EB95-485C-A5AF-D1C02FD192C8",
              "versionEndExcluding": "1.2.6"
            }
          ],
          "operator": "OR"
        }
      ]
    }
  ],
  "sourceIdentifier": "security-advisories@github.com"
}