NornicDB's Bolt Server Allows Remote Access on LAN

Summary

A vulnerability in NornicDB's Bolt server allows unauthorized remote access to the graph database on a local area network, exposing sensitive data and credentials. This occurs because the Bolt server is not properly bound to the configured address, instead listening on the wildcard address. To fix this, update to a patched version of NornicDB or use a firewall to restrict access to the Bolt port.

What to do

Update orneryd github.com/orneryd/nornicdb to version 1.0.42-hotfix.

Affected software

Ecosystem	Vendor	Product	Affected versions
Go	orneryd	github.com/orneryd/nornicdb	< 1.0.42-hotfix Fix: upgrade to 1.0.42-hotfix

Original title

Nornicdb is a distributed low-latency, Graph+Vector, Temporal MVCC with all sub-ms HNSW search, graph traversal, and writes. Prior to version 1.0.42-hotfix, the --address CLI flag (and NORNICDB_ADD...

Original description

Nornicdb is a distributed low-latency, Graph+Vector, Temporal MVCC with all sub-ms HNSW search, graph traversal, and writes. Prior to version 1.0.42-hotfix, the --address CLI flag (and NORNICDB_ADDRESS / server.host config key) is plumbed through to the HTTP server correctly but never reaches the Bolt server config. The Bolt listener therefore always binds to the wildcard address (all interfaces), regardless of what the user configures. On a LAN, this exposes the graph database — with its default admin:password credentials — to any device sharing the network. This issue has been patched in version 1.0.42-hotfix.

osv CVSS3.1 9.8

Vulnerability type

CWE-1392