Описание
NornicDB has Improper Network Binding in its Bolt Server, allowing unauthorized remote access
Summary
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.
Version
nornicdb v1.0.39- Built from commit
afe7c9donmain - Platform: macOS (darwin 25.4.0, arm64)
Reproduction
Output claims Bolt is on localhost:
But the actual socket:
HTTP port is correctly bound:
Reachable from another host on the LAN:
Setting NORNICDB_BOLT_ADDRESS=127.0.0.1 or server.host: "127.0.0.1" in config.yaml has no effect on the Bolt listener.
Root Cause
In pkg/bolt/server.go:774-776:
bolt.Config (line 474) has no Host/Address/Addr field — only Port. The CLI flag --address is stored in a local variable in cmd/nornicdb/main.go:80 and used to format user-facing log output (line 637–644), but is never copied into boltConfig at line 600–609 when Bolt is initialized.
Since ListenAndServe calls net.Listen("tcp", ":7687") with an empty host, Go binds the wildcard socket on all interfaces.
Suggested Fix
- Add a
Host stringfield tobolt.Config(default"127.0.0.1", matching the CLI flag default). - In
cmd/nornicdb/main.goaround line 601, wire it through:boltConfig.Host = address boltConfig.Port = boltPort - In
pkg/bolt/server.go:775, use the host:addr := net.JoinHostPort(s.config.Host, strconv.Itoa(s.config.Port))
Security Impact
- Default
admin:passwordcredentials + wildcard binding = anyone on the same WiFi can issue arbitrary Cypher queries (read, write, delete nodes) against NornicDB instances running with default setup. - Users following the README will reasonably assume
--address 127.0.0.1(the documented default) binds both protocols to localhost. - Workaround: host-firewall rules (e.g. macOS
pf) blocking non-loopback → 7687. Not discoverable from the docs.
Ссылки
- https://github.com/orneryd/NornicDB/security/advisories/GHSA-2hp7-65r3-wv54
- https://nvd.nist.gov/vuln/detail/CVE-2026-42072
- https://github.com/orneryd/NornicDB/commit/adce4f9a9fc7b6aada07c0bfa2d737cd7a6efaca
- https://github.com/orneryd/NornicDB/releases/tag/v1.0.42
- https://github.com/orneryd/NornicDB/releases/tag/v1.0.42-hotfix
Пакеты
github.com/orneryd/nornicdb
< 1.0.42-hotfix
1.0.42-hotfix
Связанные уязвимости
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.