{"answers":{"affected":"2 open source packages ship an affected version, including org.graylog:graylog-parent. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-15813 in the wild and no public exploit code.","fix":"Upgrade org.graylog:graylog-parent to 3.3.3 or later.","what":"CVE-2020-15813 is a high-severity authentication bypass vulnerability in n/a, published on 17 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-15813 and fix it if it is affected.\n\nWhat it is: CVE-2020-15813 is a high-severity authentication bypass vulnerability in n/a, published on 17 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-15813 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.graylog:graylog-parent (Maven): affected all versions; fixed in 3.3.3\n- org.graylog:graylog-parent (Maven): affected all versions; fixed in 3.3.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-2020-15813/ (Markdown: https://insights.sbomify.com/CVE-2020-15813/index.md)","id":"CVE-2020-15813","markdown":"https://insights.sbomify.com/CVE-2020-15813/index.md","name":"CVE-2020-15813","record":{"aliases":["GHSA-3gg9-f3vh-866f"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Graylog log management","requires_auth":"none","summary":"Attackers can bypass authentication by intercepting traffic to a malicious LDAP server due to missing SSL certificate validation in Graylog.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"graylog","vendor":"graylog"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"Graylog before 3.3.3 lacks SSL Certificate Validation for LDAP servers. It allows use of an external user/group database stored in LDAP. The connection configuration allows the usage of unencrypted, SSL- or TLS-secured connections. Unfortunately, the Graylog client code (in all versions that support LDAP) does not implement proper certificate validation (regardless of whether the \"Allow self-signed certificates\" option is used). Therefore, any attacker with the ability to intercept network traffic between a Graylog server and an LDAP server is able to redirect traffic to a different LDAP server (unnoticed by the Graylog server due to the lack of certificate validation), effectively bypassing Graylog's authentication mechanism.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Improper Certificate Validation in Graylog","id":"CVE-2020-15813","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"auth_bypass","year":"2020"},"n_packages":2,"n_references":1,"next":{"headline":"In Western Digital WD Discovery before 4.0.251.0, a malicious application running with standard user permissions could potentially execute c","id":"CVE-2020-15816"},"packages":[{"ecosystem":"Maven","fixed":["3.3.3"],"introduced":["0"],"last_affected":[],"package":"org.graylog:graylog-parent","purl":null,"source":"GHSA-3gg9-f3vh-866f"},{"ecosystem":"Maven","fixed":["3.3.3"],"introduced":["0"],"last_affected":[],"package":"org.graylog:graylog-parent","purl":"pkg:maven/org.graylog/graylog-parent","source":"GHSA-3gg9-f3vh-866f"}],"prev":{"headline":"Other in n/a","id":"CVE-2020-15811"},"products":["n/a"],"published":"2020-07-17","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,"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can bypass authentication by intercepting traffic to a malicious LDAP server due to missing SSL certificate validation in Graylog.","url":"https://insights.sbomify.com/CVE-2020-15813/"}