CVE-2018-18389
published 2018-10-16CVE-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…
PriorityP260critical9.8CVSS 3.0
AVNACLPRNUINSUCHIHAH
EPSS
1.92%
77.3th percentile
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.
Affected
1 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| neo4j | neo4j | >= 3.4.0 < 3.4.9 | 3.4.9 |
CVSS provenance
nvdv3.09.8CRITICALCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvdv2.07.5HIGHAV:N/AC:L/Au:N/C:P/I:P/A:P
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
Incorrect access control in Neo4j Enterprise Database Server via LDAP authentication
ghsa·2018-10-17
CVE-2018-18389 [CRITICAL] CWE-287 Incorrect access control in Neo4j Enterprise Database Server via LDAP authentication
Incorrect access control in Neo4j Enterprise Database Server via LDAP authentication
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.
OSV
Incorrect access control in Neo4j Enterprise Database Server via LDAP authentication
osv·2018-10-17
CVE-2018-18389 [CRITICAL] Incorrect access control in Neo4j Enterprise Database Server via LDAP authentication
Incorrect access control in Neo4j Enterprise Database Server via LDAP authentication
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.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2018-10-16
Published