CVE-2025-32030

{"id": "CVE-2025-32030", "cveTags": [], "metrics": {"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}]}, "published": "2025-04-07T21:15:43.037", "references": [{"url": "https://github.com/apollographql/federation/pull/3236", "source": "security-advisories@github.com"}, {"url": "https://github.com/apollographql/federation/releases/tag/%40apollo%2Fgateway%402.10.1", "source": "security-advisories@github.com"}, {"url": "https://github.com/apollographql/federation/security/advisories/GHSA-q2f9-x4p4-7xmh", "source": "security-advisories@github.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Primary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-770"}]}], "descriptions": [{"lang": "en", "value": "Apollo Gateway provides utilities for combining multiple GraphQL microservices into a single GraphQL endpoint. Prior to 2.10.1, a vulnerability in Apollo Gateway allowed queries with deeply nested and reused named fragments to be prohibitively expensive to query plan, specifically during named fragment expansion. Named fragments were being expanded once per fragment spread during query planning, leading to exponential resource usage when deeply nested and reused fragments were involved. This could lead to excessive resource consumption and denial of service. This has been remediated in @apollo/gateway version 2.10.1."}, {"lang": "es", "value": "Apollo Gateway proporciona utilidades para combinar m\u00faltiples microservicios GraphQL en un \u00fanico endpoint GraphQL. Antes de la versi\u00f3n 2.10.1, una vulnerabilidad en Apollo Gateway hac\u00eda que las consultas con fragmentos con nombre profundamente anidados y reutilizados fueran excesivamente costosas de planificar, especialmente durante la expansi\u00f3n de fragmentos con nombre. Los fragmentos con nombre se expand\u00edan una vez por cada fragmento extendido durante la planificaci\u00f3n, lo que provocaba un uso exponencial de recursos al involucrar fragmentos profundamente anidados y reutilizados. Esto pod\u00eda provocar un consumo excesivo de recursos y denegaci\u00f3n de servicio. Esto se ha solucionado en la versi\u00f3n 2.10.1 de @apollo/gateway."}], "lastModified": "2025-04-08T18:13:53.347", "sourceIdentifier": "security-advisories@github.com"}