{"answers":{"affected":"4 open source packages ship an affected version, including org.graylog2:graylog2-server. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-41045 exists.","fix":"Upgrade org.graylog2:graylog2-server to a fixed version for your release line: 5.0.9 or 5.1.3.","what":"CVE-2023-41045 is a low-severity vulnerability in graylog2-server, published on 31 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-41045 and fix it if it is affected.\n\nWhat it is: CVE-2023-41045 is a low-severity vulnerability in graylog2-server, published on 31 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-41045 exists.\n\nAffected packages and fixed versions:\n- org.graylog2:graylog2-server (Maven): affected all versions; fixed in 5.0.9\n- org.graylog2:graylog2-server (Maven): affected all versions; fixed in 5.0.9\n- org.graylog2:graylog2-server (Maven): affected from 5.1.0; fixed in 5.1.3\n- org.graylog2:graylog2-server (Maven): affected from 5.1.0; fixed in 5.1.3\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-41045/ (Markdown: https://insights.sbomify.com/CVE-2023-41045/index.md)","id":"CVE-2023-41045","markdown":"https://insights.sbomify.com/CVE-2023-41045/index.md","name":"CVE-2023-41045","record":{"aliases":["GHSA-g96c-x7rh-99r3"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Graylog log management","requires_auth":"none","summary":"An attacker can inject forged DNS responses into Graylog's lookup table cache due to static source port usage, potentially altering data or bypassing security checks.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"graylog","vendor":"graylog"}],"cvss":{"score":3.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Insecure source port usage for DNS queries in Graylog","id":"CVE-2023-41045","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"other","year":"2023"},"n_packages":4,"n_references":3,"next":{"headline":"Velocity execution without script rights in Xwiki platform","id":"CVE-2023-41046"},"packages":[{"ecosystem":"Maven","fixed":["5.0.9"],"introduced":["0"],"last_affected":[],"package":"org.graylog2:graylog2-server","purl":null,"source":"GHSA-g96c-x7rh-99r3"},{"ecosystem":"Maven","fixed":["5.0.9"],"introduced":["0"],"last_affected":[],"package":"org.graylog2:graylog2-server","purl":"pkg:maven/org.graylog2/graylog2-server","source":"GHSA-g96c-x7rh-99r3"},{"ecosystem":"Maven","fixed":["5.1.3"],"introduced":["5.1.0"],"last_affected":[],"package":"org.graylog2:graylog2-server","purl":null,"source":"GHSA-g96c-x7rh-99r3"},{"ecosystem":"Maven","fixed":["5.1.3"],"introduced":["5.1.0"],"last_affected":[],"package":"org.graylog2:graylog2-server","purl":"pkg:maven/org.graylog2/graylog2-server","source":"GHSA-g96c-x7rh-99r3"}],"prev":{"headline":"Partial path traversal vulnerability in Support Bundle feature of Graylog","id":"CVE-2023-41044"},"products":["graylog2-server"],"published":"2023-08-31","related":[{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2021-37759","kev_date_added":null,"published":"2021-07-31"},{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2021-37760","kev_date_added":null,"published":"2021-07-31"},{"cvss_score":9.3,"headline":"Incorrect management of session invalidation vulnerability in Graylog Web Interface","id":"CVE-2026-1435","kev_date_added":null,"published":"2026-02-18"},{"cvss_score":8.8,"headline":"Graylog vulnerable to privilege escalation through API tokens","id":"CVE-2025-53106","kev_date_added":null,"published":"2025-07-02"},{"cvss_score":8.8,"headline":"graylog2-server vulnerable to instantiation of arbitrary classes triggered by API request","id":"CVE-2024-24824","kev_date_added":null,"published":"2024-02-07"},{"cvss_score":8.1,"headline":"Improper Certificate Validation in Graylog","id":"CVE-2020-15813","kev_date_added":null,"published":"2020-07-17"},{"cvss_score":8,"headline":"Graylog Allows Session Takeover via Insufficient HTML Sanitization","id":"CVE-2025-46827","kev_date_added":null,"published":"2025-05-07"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-10-01","vendors":["Graylog2"]},"summary":"An attacker can inject forged DNS responses into Graylog's lookup table cache due to static source port usage, potentially altering data or bypassing security checks.","url":"https://insights.sbomify.com/CVE-2023-41045/"}