DEV Community

andreagomez
andreagomez

Posted on

Neo4j Browser turns graph access into an internet-visible query surface

Neo4j Browser turns graph access into an internet-visible query surface

Neo4j Browser is a query and visualization interface for Neo4j databases. It connects to an instance through Bolt and lets an authenticated user run Cypher. The Browser documentation presents it as part of the server and cloud offerings, not as a stand-alone authorization layer. Authentication and authorization are properties of the database and its configured providers.

That distinction is the core inventory question. A Browser page on the internet may lead to a database that requires a strong login, or it may lead to an instance with authentication disabled. The Browser title or product fingerprint cannot answer which case applies. The database listener, authentication configuration, user roles, and network path must be checked separately.

The Browser credential documentation adds a practical detail for shared environments: connection credentials are cached in the browser's session storage, and the documentation says this caching can no longer be disabled through the legacy server setting. A shared workstation, a browser extension, or an injected script can therefore interact with the stored connection state even when the database itself uses strong authentication.

Query plan

The reproducible candidates are app="Neo4j Browser" and title="Neo4j Browser" with sub_type=all, page 1, and page size 1. The title may also appear in documentation or a desktop page, while the application field may describe a bundled component rather than a separate host. No live counts were collected in this run because the authorized ZoomEye execution path was rejected by the execution platform.

Treat the query as a discovery aid. Confirm ownership and service scope before opening the page or attempting a connection. If you are authorized to test the service, use an account created for the review and do not run queries that modify the graph.

Inventory the database boundary

List Neo4j instances, their Browser exposure, the Bolt endpoint, the HTTP interface, and the authentication provider. The authenticated path should be documented for administrators, application drivers, and read-only users. If authentication is disabled, the exposure is not a Browser-interface problem alone. Any client that can reach the database may execute Cypher with the server's authority.

Review roles and privileges for the graph. A role that can manage users, databases, or procedures has more authority than a role that can read a bounded label. Test a read-only user with the same query patterns the application uses. Confirm that an unauthenticated request is rejected and that a disabled user cannot reuse a driver session.

Inspect the Bolt and HTTP listeners separately. Browser may be served by one process while application drivers connect to another port. A firewall rule that protects the UI but leaves Bolt reachable from an application subnet may be intentional, but it still needs an identity and network review.

Review the browser client

Clear session storage on shared machines and use separate browser profiles for administrative work. Review extensions and proxy settings that can change the Bolt endpoint or read page state. A Browser user can display graph data and query history in the page; support screenshots should be classified accordingly.

Monitor authentication failures, privilege changes, and unusually broad queries. The database may log query text, parameters, and user identity depending on configuration. Keep retention and access controls aligned with the sensitivity of the graph. Do not place database passwords in query text or application logs.

Respond to a match

Verify the owner through inventory and DNS. If the instance is yours, check the authentication setting, Browser route, exposed listeners, and recent role changes. If the instance is not authorized, isolate it rather than attempting a login. A Browser title alone does not prove a vulnerable database, but it is a useful prompt to inspect the identity and query boundary.

Neo4j Browser is a window into a powerful graph engine. The meaningful security control is the database identity and the network path that reaches it. Inventory the window, then prove what the database allows behind it.

References

Top comments (0)