Vulnerabilities · 2018 · Neo4j
CVE-2018-18389
Neo4j vulnerability
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.
High priority: this vulnerability is rated critical and can be attacked over the network without a login.
Affected products
Neo4j. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Neo4j runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
More vulnerabilities in Neo4j products
CVE-2024-34517CVE-2023-23926CVE-2022-37423CVE-2022-23532CVE-2021-42767CVE-2021-34802CVE-2021-34371CVE-2018-1000820All 10
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.