Incorrect access control in Neo4j Enterprise Database Server via LDAP authentication
Critical severity
GitHub Reviewed
Published
Oct 17, 2018
to the GitHub Advisory Database
•
Updated Apr 5, 2023
Package
Affected versions
>= 3.4.0, < 3.4.9
Patched versions
3.4.9
Description
Published to the GitHub Advisory Database
Oct 17, 2018
Reviewed
Jun 16, 2020
Last updated
Apr 5, 2023
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.
References