xkeys Seal encryption used fixed key for all encryption
nats-io nkeys
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/nats-io/nkeys Go |
|
|
| github.com/nats-io/nats-server/v2 Go |
|
|
nats-io nkeys
| Product | Affected | Fixed in |
|---|---|---|
| github.com/nats-io/nkeys Go |
|
|
| github.com/nats-io/nats-server/v2 Go |
|
|
NATS.io is a high performance open source pub-sub distributed communication technology, built for the cloud, on-premise, IoT, and edge computing. The cryptographic key handling library, nkeys, recently gained support for encryption, not just for signing/authentication. This is used in nats-server 2.10 (Sep 2023) and newer for authentication callouts. In nkeys versions 0.4.0 through 0.4.5, corresponding with NATS server versions 2.10.0 through 2.10.3, the nkeys library's `xkeys` encryption handling logic mistakenly passed an array by value into an internal function, where the function mutated that buffer to populate the encryption key to use. As a result, all encryption was actually to an all-zeros key. This affects encryption only, not signing. FIXME: FILL IN IMPACT ON NATS-SERVER AUTH CALLOUT SECURITY. nkeys Go library 0.4.6, corresponding with NATS Server 2.10.4, has a patch for this issue. No known workarounds are available. For any application handling auth callouts in Go, if using the nkeys library, update the dependency, recompile and deploy that in lockstep.
From the CVE record · GitHub_M
Affected nkeys versions encrypt with an all-zero key because of a buffer-handling error in xkeys. This affects encryption used for NATS Server authentication callouts, but not signing; it could expose encrypted data to someone who obtains it. The input does not specify whether exploitation requires network or local access, authentication, or user interaction.
Teams running Go github.com/nats-io/nkeys >=0.4.0 <0.4.6 or github.com/nats-io/nats-server/v2 >=2.10.0 <2.10.4 should check their deployments.