{"answers":{"affected":"2 open source packages ship an affected version, including org.neo4j:neo4j-enterprise. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-18389 in the wild and no public exploit code.","fix":"Upgrade org.neo4j:neo4j-enterprise to 3.4.9 or later.","what":"CVE-2018-18389 is a critical authentication bypass vulnerability in n/a, published on 16 Oct 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-18389 and fix it if it is affected.\n\nWhat it is: CVE-2018-18389 is a critical authentication bypass vulnerability in n/a, published on 16 Oct 2018. 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-2018-18389 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.neo4j:neo4j-enterprise (Maven): affected from 3.4.0; fixed in 3.4.9\n- org.neo4j:neo4j-enterprise (Maven): affected from 3.4.0; fixed in 3.4.9\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-2018-18389/ (Markdown: https://insights.sbomify.com/CVE-2018-18389/index.md)","id":"CVE-2018-18389","markdown":"https://insights.sbomify.com/CVE-2018-18389/index.md","name":"CVE-2018-18389","record":{"aliases":["GHSA-h5f5-rj4r-42f6"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Neo4j Enterprise Database","requires_auth":"none","summary":"Attackers can bypass authentication and log into Neo4j Enterprise Database by exploiting incorrect access control in specific LDAP and System Account configurations.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"neo4j","vendor":"neo4j"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"Due to incorrect access control in Neo4j Enterprise Database Server 3.4.x before 3.4.9, the setting of LDAP for authentication with STARTTLS, and System Account for authorization, allows an attacker to log into the server by sending any valid username with an arbitrary password.","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":"Incorrect access control in Neo4j Enterprise Database Server via LDAP authentication","id":"CVE-2018-18389","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"auth_bypass","year":"2018"},"n_packages":2,"n_references":1,"next":{"headline":"Information disclosure in ThingsPro IIoT Gateway and Device Management Software Solutions","id":"CVE-2018-18390"},"packages":[{"ecosystem":"Maven","fixed":["3.4.9"],"introduced":["3.4.0"],"last_affected":[],"package":"org.neo4j:neo4j-enterprise","purl":null,"source":"GHSA-h5f5-rj4r-42f6"},{"ecosystem":"Maven","fixed":["3.4.9"],"introduced":["3.4.0"],"last_affected":[],"package":"org.neo4j:neo4j-enterprise","purl":"pkg:maven/org.neo4j/neo4j-enterprise","source":"GHSA-h5f5-rj4r-42f6"}],"prev":{"headline":"Command injection in n/a","id":"CVE-2018-18388"},"products":["n/a"],"published":"2018-10-16","related":[{"cvss_score":9.8,"headline":"Deserialization of Untrusted Data in Neo4j","id":"CVE-2021-34371","kev_date_added":null,"published":"2021-08-05"},{"cvss_score":6.8,"headline":"Neo4J vulnerable to Cross-Site Request Forgery","id":"CVE-2013-7259","kev_date_added":null,"published":"2014-04-29"},{"cvss_score":6.5,"headline":"Neo4j Cypher component mishandles IMMUTABLE privileges","id":"CVE-2024-34517","kev_date_added":null,"published":"2024-05-07"},{"cvss_score":5.5,"headline":"Unathenticated connection can hold Bolt channel open","id":"CVE-2026-14587","kev_date_added":null,"published":"2026-08-05"},{"cvss_score":2.1,"headline":"Caching of authentication context","id":"CVE-2026-1471","kev_date_added":null,"published":"2026-03-11"},{"cvss_score":2.1,"headline":"Auth misconfiguration when multiple providers enabled","id":"CVE-2026-1524","kev_date_added":null,"published":"2026-03-11"}],"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-09-16","vendors":["n/a"]},"summary":"Attackers can bypass authentication and log into Neo4j Enterprise Database by exploiting incorrect access control in specific LDAP and System Account configurations.","url":"https://insights.sbomify.com/CVE-2018-18389/"}