CVE-2018-18389: Incorrect access control in Neo4j Enterprise Database Server via LDAP authentication
Summary
CVE-2018-18389: Incorrect access control in Neo4j Enterprise Database Server via LDAP authentication. Affects org.neo4j:neo4j-enterprise versions >= 3.4.0, < 3.4.9. Fixed in 3.4.9. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
Neo4j Enterprise Database Server is a powerful database management system that allows users to store, query, and manipulate highly connected data. It provides a scalable and reliable solution for managing complex relationships between entities. The LDAP authentication feature in Neo4j Enterprise Database Server allows users to authenticate using LDAP credentials, providing an additional layer of security. However, a vulnerability in versions 3.4.x before 3.4.9 allows attackers to bypass the authentication process and gain unauthorized access to the server.
Vulnerability Detail
The vulnerability arises from incorrect access control in the LDAP authentication process. When LDAP authentication is configured with STARTTLS and a System Account for authorization, an attacker can log into the server by sending any valid username with an arbitrary password. This means that an attacker can bypass the authentication mechanism and gain unauthorized access to the Neo4j Enterprise Database Server. The impact of this vulnerability is severe, as it allows an attacker to potentially view, modify, or delete sensitive data stored in the database.
How To Fix
Minimum fixed version
3.4.9
This is the first release that contains the fix.
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
There is no known workaround for this vulnerability. It is essential to upgrade to the fixed version of Neo4j Enterprise Database Server to address the issue.
Conclusion
In conclusion, the vulnerability in Neo4j Enterprise Database Server allows attackers to bypass LDAP authentication and gain unauthorized access to the server. To mitigate this risk, it is crucial to upgrade to version 3.4.9 or later. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for org.neo4j:neo4j-enterprise →
FAQ
Neo4j Enterprise Database Server is a powerful database management system that allows users to store, query, and manipulate highly connected data. It provides a scalable and reliable solution for managing complex relationships between entities.
LDAP authentication is a method of verifying the identity of a user by using the Lightweight Directory Access Protocol (LDAP). It allows users to authenticate using their LDAP credentials, which are stored in a directory server.
STARTTLS is a command used in the LDAP protocol to enable encryption of the communication between the client and the server. It ensures that the authentication process is secure and protected from eavesdropping or tampering.
A System Account in Neo4j Enterprise Database Server is a privileged account that is used for administrative tasks and authorization. It has elevated privileges and can perform actions that regular user accounts cannot.
This vulnerability allows an attacker to bypass the authentication process and gain unauthorized access to the Neo4j Enterprise Database Server. The attacker can potentially view, modify, or delete sensitive data stored in the database, leading to a breach of confidentiality, integrity, and availability.
References
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
