« Volver al listado

CVE-2025-29785

Estado: AplazadaAlta (7.5)—

quic-go is an implementation of the QUIC protocol in Go. The loss recovery logic for path probe packets that was added in the v0.50.0 release can be used to trigger a nil-pointer dereference by a malicious QUIC client. In order to do so, the attacker first sends valid QUIC packets from different remote addresses (thereby triggering the newly added path validation logic: the server sends path probe packets), and then sending ACKs for packets received from the server specifically crafted to trigger the nil-pointer dereference. v0.50.1 contains a patch that fixes the vulnerability.

Leer descripción completaMostrar menos

This release contains a test that generates random sequences of sent packets (both regular and path probe packets), that was used to verify that the patch actually covers all corner cases. No known workarounds are available.

CVSS

Probabilidad de explotación (EPSS)

EPSS (Exploit Prediction Scoring System, de FIRST) estima la probabilidad de que una vulnerabilidad sea explotada en 30 días. Complementa a CVSS (impacto) y a CISA KEV (explotación confirmada).

🎯 Técnicas ATT&CK

Cómo se explota esta vulnerabilidad y qué consigue el atacante, en el lenguaje de MITRE ATT&CK.

Vector CVSS AV:N/AC:L/PR:N indica explotación remota sin autenticación (T1190). La nil-pointer dereference causa DoS por crash del servidor QUIC (T1499.004), confirmado por CWE-248 y descripción de pérdida de disponibilidad (A:H).

Inferido por nuestro agente de análisis a partir de la descripción oficial, el vector CVSS y la CWE, y comprobado por un supervisor. Puede contener errores.

🛡️ Mitigaciones ATT&CK que cubren estas técnicas

Filter Network TrafficVulnerability ScanningPrivileged Account ManagementNetwork SegmentationLimit Access to Resource Over NetworkApplication Isolation and Sandboxing

Tecnologías afectadas (1)

⚠ Inferidas por IA a partir de la descripción — NVD aún no ha analizado esta CVE; no son CPE verificados.

Quic-go — Quic-goAI

CWE

Referencias

JSON original (NVD)

Mostrar
{
  "id": "CVE-2025-29785",
  "cveTags": [],
  "metrics": {
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2025-29785",
          "role": "CISA Coordinator",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "yes"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "version": "2.0.3",
          "timestamp": "2025-06-02T12:00:53.410884Z"
        }
      }
    ],
    "cvssMetricV31": [
      {
        "type": "Secondary",
        "source": "security-advisories@github.com",
        "cvssData": {
          "scope": "UNCHANGED",
          "version": "3.1",
          "baseScore": 7.5,
          "attackVector": "NETWORK",
          "baseSeverity": "HIGH",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
          "integrityImpact": "NONE",
          "userInteraction": "NONE",
          "attackComplexity": "LOW",
          "availabilityImpact": "HIGH",
          "privilegesRequired": "NONE",
          "confidentialityImpact": "NONE"
        },
        "impactScore": 3.6,
        "exploitabilityScore": 3.9
      }
    ]
  },
  "affected": [
    {
      "source": "security-advisories@github.com",
      "affectedData": [
        {
          "vendor": "quic-go",
          "product": "quic-go",
          "versions": [
            {
              "status": "affected",
              "version": "= 0.50.0"
            }
          ]
        }
      ]
    }
  ],
  "published": "2025-06-02T11:15:21.953",
  "references": [
    {
      "url": "https://github.com/quic-go/quic-go/commit/b90058aba5f65f48e0e150c89bbaa21a72dda4de",
      "source": "security-advisories@github.com"
    },
    {
      "url": "https://github.com/quic-go/quic-go/issues/4981",
      "source": "security-advisories@github.com"
    },
    {
      "url": "https://github.com/quic-go/quic-go/security/advisories/GHSA-j972-j939-p2v3",
      "source": "security-advisories@github.com"
    }
  ],
  "vulnStatus": "Deferred",
  "weaknesses": [
    {
      "type": "Secondary",
      "source": "security-advisories@github.com",
      "description": [
        {
          "lang": "en",
          "value": "CWE-248"
        }
      ]
    }
  ],
  "descriptions": [
    {
      "lang": "en",
      "value": "quic-go is an implementation of the QUIC protocol in Go. The loss recovery logic for path probe packets that was added in the v0.50.0 release can be used to trigger a nil-pointer dereference by a malicious QUIC client. In order to do so, the attacker first sends valid QUIC packets from different remote addresses (thereby triggering the newly added path validation logic: the server sends path probe packets), and then sending ACKs for packets received from the server specifically crafted to trigger the nil-pointer dereference. v0.50.1 contains a patch that fixes the vulnerability. This release contains a test that generates random sequences of sent packets (both regular and path probe packets), that was used to verify that the patch actually covers all corner cases. No known workarounds are available."
    },
    {
      "lang": "es",
      "value": "quic-go es una implementación del protocolo QUIC en Go. La lógica de recuperación de pérdidas para paquetes de sondeo de ruta, añadida en la versión v0.50.0, puede utilizarse para que un cliente QUIC malicioso active una desreferencia de puntero nulo. Para ello, el atacante primero envía paquetes QUIC válidos desde diferentes direcciones remotas (activando así la nueva lógica de validación de ruta: el servidor envía paquetes de sondeo de ruta) y, a continuación, envía ACKs para los paquetes recibidos del servidor, diseñados específicamente para activar la desreferencia de puntero nulo. La versión v0.50.1 incluye un parche que corrige la vulnerabilidad. Esta versión incluye una prueba que genera secuencias aleatorias de paquetes enviados (tanto paquetes normales como de sondeo de ruta), que se utilizó para verificar que el parche cubre todos los casos excepcionales. No se conocen workarounds."
    }
  ],
  "lastModified": "2026-06-17T09:05:40.050",
  "sourceIdentifier": "security-advisories@github.com"
}