CVE-2023-41045

{"id": "CVE-2023-41045", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2023-41045", "role": "CISA Coordinator", "options": [{"exploitation": "poc"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2024-10-01T16:55:58.051737Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 3.7, "attackVector": "NETWORK", "baseSeverity": "LOW", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 1.4, "exploitabilityScore": 2.2}, {"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 1.4, "exploitabilityScore": 3.9}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "Graylog2", "product": "graylog2-server", "versions": [{"status": "affected", "version": "< 5.0.9"}, {"status": "affected", "version": ">= 5.1.0, < 5.1.3"}]}]}], "published": "2023-08-31T18:15:09.280", "references": [{"url": "https://github.com/Graylog2/graylog2-server/commit/466af814523cffae9fbc7e77bab7472988f03c3e", "tags": ["Patch"], "source": "security-advisories@github.com"}, {"url": "https://github.com/Graylog2/graylog2-server/commit/a101f4f12180fd3dfa7d3345188a099877a3c327", "tags": ["Patch"], "source": "security-advisories@github.com"}, {"url": "https://github.com/Graylog2/graylog2-server/security/advisories/GHSA-g96c-x7rh-99r3", "tags": ["Exploit", "Vendor Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/Graylog2/graylog2-server/commit/466af814523cffae9fbc7e77bab7472988f03c3e", "tags": ["Patch"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/Graylog2/graylog2-server/commit/a101f4f12180fd3dfa7d3345188a099877a3c327", "tags": ["Patch"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/Graylog2/graylog2-server/security/advisories/GHSA-g96c-x7rh-99r3", "tags": ["Exploit", "Vendor Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-345"}]}], "descriptions": [{"lang": "en", "value": "Graylog is a free and open log management platform. Graylog makes use of only one single source port for DNS queries. Graylog binds a single socket for outgoing DNS queries and while that socket is bound to a random port number it is never changed again. This goes against recommended practice since 2008, when Dan Kaminsky discovered how easy is to carry out DNS cache poisoning attacks. In order to prevent cache poisoning with spoofed DNS responses, it is necessary to maximise the uncertainty in the choice of a source port for a DNS query. Although unlikely in many setups, an external attacker could inject forged DNS responses into a Graylog's lookup table cache. In order to prevent this, it is at least recommendable to distribute the DNS queries through a pool of distinct sockets, each of them with a random source port and renew them periodically. This issue has been addressed in versions 5.0.9 and 5.1.3. Users are advised to upgrade. There are no known workarounds for this issue."}, {"lang": "es", "value": "Graylog es una plataforma de gesti\u00f3n de logs gratuita y de c\u00f3digo abierto. Graylog utiliza solo un \u00fanico puerto de origen para las consultas DNS. Graylog enlaza un \u00fanico socket para las consultas DNS salientes y, aunque ese socket est\u00e1 enlazado a un n\u00famero de puerto aleatorio, nunca se vuelve a cambiar. Esto va en contra de la pr\u00e1ctica recomendada desde 2008, cuando Dan Kaminsky descubri\u00f3 lo f\u00e1cil que es llevar a cabo ataques de envenenamiento de cach\u00e9 DNS. Para evitar el envenenamiento de cach\u00e9 con respuestas DNS falsificadas, es necesario maximizar la incertidumbre en la elecci\u00f3n de un puerto de origen para una consulta DNS. Aunque improbable en muchas configuraciones, un atacante externo podr\u00eda inyectar respuestas DNS falsificadas en la cach\u00e9 de la tabla de b\u00fasqueda de Graylog. Para evitar esto, es al menos recomendable distribuir las consultas DNS a trav\u00e9s de un pool de sockets distintos, cada uno de ellos con un puerto de origen aleatorio y renovarlos peri\u00f3dicamente. Este problema ha sido abordado en las versiones 5.0.9 y 5.1.3. Se aconseja a los usuarios actualizar. No se conocen soluciones alternativas para este problema."}], "lastModified": "2026-06-17T06:20:16.213", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:graylog:graylog:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "F94DC8EE-E1C4-472F-B479-12A35C92D2C8", "versionEndExcluding": "5.0.9"}, {"criteria": "cpe:2.3:a:graylog:graylog:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "E213B603-847C-439D-86AA-D77E59653492", "versionEndExcluding": "5.1.3", "versionStartIncluding": "5.1.0"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}