CVE-2025-31496

{"id": "CVE-2025-31496", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "[email protected]", "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:42.720", "references": [{"url": "https://github.com/apollographql/apollo-rs/pull/952", "source": "[email protected]"}, {"url": "https://github.com/apollographql/apollo-rs/security/advisories/GHSA-7mpv-9xg6-5r79", "source": "[email protected]"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Primary", "source": "[email protected]", "description": [{"lang": "en", "value": "CWE-770"}]}], "descriptions": [{"lang": "en", "value": "apollo-compiler is a query-based compiler for the GraphQL query language. Prior to 1.27.0, a vulnerability in Apollo Compiler allowed queries with deeply nested and reused named fragments to be prohibitively expensive to validate. Named fragments were being processed once per fragment spread in some cases during query validation, leading to exponential resource usage when deeply nested and reused fragments were involved. This could lead to excessive resource consumption and denial of service in applications. This vulnerability is fixed in 1.27.0."}, {"lang": "es", "value": "apollo-compiler es un compilador basado en consultas para el lenguaje de consulta GraphQL. Antes de la versi\u00f3n 1.27.0, una vulnerabilidad en Apollo Compiler hac\u00eda que la validaci\u00f3n de consultas con fragmentos con nombre profundamente anidados y reutilizados fuera extremadamente costosa. En algunos casos, los fragmentos con nombre se procesaban una vez por fragmento distribuido durante la validaci\u00f3n de consultas, lo que provocaba un consumo exponencial de recursos al usar fragmentos profundamente anidados y reutilizados. Esto pod\u00eda provocar un consumo excesivo de recursos y denegaci\u00f3n de servicio en las aplicaciones. Esta vulnerabilidad se corrigi\u00f3 en la versi\u00f3n 1.27.0."}], "lastModified": "2025-04-08T18:13:53.347", "sourceIdentifier": "[email protected]"}