Critical severity · published Oct 16, 2018
CVE-2018-18389
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,…
9.8
CVSS
1.9%
EPSS
No
On KEV
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.
CVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
High
Integrity
High
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)1.9% · higher than 80% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
NE
Neo4j · Neo4j
3.4.0 before 3.4.9 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2018-18389
CVE.org
https://www.cve.org/CVERecord?id=CVE-2018-18389
Exploit
https://github.com/neo4j/neo4j/issues/12047
More from Neo4j
9.8
CVE-2026-1524
Auth misconfiguration when multiple providers enabled
9.8
CVE-2021-34371
Neo4j through 3.4.18 (with the shell server enabled) exposes an RMI service that arbitrarily deserializes Java objects, e.g., through setSessionVariable
7.5
CVE-2026-14587
Unathenticated connection can hold Bolt channel open
7.2
CVE-2026-1497
Incorrect privilege assignment in composite databases
6.5
CVE-2026-1471
Caching of authentication context