CVE-2025-30193

{"id": "CVE-2025-30193", "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-05-20T12:15:19.697", "references": [{"url": "https://dnsdist.org/security-advisories/powerdns-advisory-for-dnsdist-2025-03.html", "source": "[email protected]"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "[email protected]", "description": [{"lang": "en", "value": "CWE-674"}]}], "descriptions": [{"lang": "en", "value": "In some circumstances, when DNSdist is configured to allow an unlimited number of queries on a single, incoming TCP connection from a client, an attacker can cause a denial of service by crafting a TCP exchange that triggers an exhaustion of the stack and a crash of DNSdist, causing a denial of service.\n\nThe remedy is: upgrade to the patched 1.9.10 version.\n\nA workaround is to restrict the maximum number of queries on incoming TCP connections to a safe value, like 50, via the setMaxTCPQueriesPerConnection setting.\n\nWe would like to thank Renaud Allard for bringing this issue to our attention."}, {"lang": "es", "value": "En algunas circunstancias, cuando DNSdist est\u00e1 configurado para permitir un n\u00famero ilimitado de consultas en una \u00fanica conexi\u00f3n TCP entrante desde un cliente, un atacante puede provocar una denegaci\u00f3n de servicio manipulando un intercambio TCP que provoca el agotamiento de la pila y un bloqueo de DNSdist, lo que provoca una denegaci\u00f3n de servicio. La soluci\u00f3n es actualizar a la versi\u00f3n 1.9.10 con el parche. Una alternativa consiste en restringir el n\u00famero m\u00e1ximo de consultas en las conexiones TCP entrantes a un valor seguro, como 50, mediante la configuraci\u00f3n setMaxTCPQueriesPerConnection. Agradecemos a Renaud Allard por informarnos sobre este problema."}], "lastModified": "2025-05-21T20:25:16.407", "sourceIdentifier": "[email protected]"}