VDB
Sign up
MEDIUM6.5

GHSA-p3j5-5hrq-p75h

nats-server Leaf node connections bypass Nats-Trace-Dest permission check

Quick fix

GHSA-p3j5-5hrq-p75h — github.com/nats-io/nats-server/v2: upgrade to the fixed version with the command below.

go get github.com/nats-io/nats-server/v2@v2.12.8

Details

### Background

NATS.io is a high performance open source pub-sub distributed communication technology, built for the cloud, on-premise, IoT and edge computing.

The NATS Server supports leafnode connections between servers and message tracing through NATS headers.

### Problem Description

Message trace destination checks were applied to ordinary client connections but not consistently to messages arriving through leafnode connections.

A leafnode operator could cause trace events to be sent to subjects that would not otherwise be permitted and could use trace-only behavior to prevent normal delivery or storage of affected messages.

Trace events can include routing, subscription, account, service import and JetStream metadata. The payload of the original application message is not chosen through the trace event itself.

### Affected Versions

Versions v2.14.2, v2.12.7 and below are vulnerable. The issue is fixed in v2.14.3 and v2.12.8.

### Workarounds

Where possible, avoid granting publish paths from less-trusted leaf nodes into subjects for which trace-only behavior would affect delivery guarantees. No other known workarounds are available aside from upgrading to a fixed release.

### References

* GHSA advisory: <https://github.com/nats-io/nats-server/security/advisories/GHSA-p3j5-5hrq-p75h> * Credit: Koda Reef

Are you affected?

Enter the version of the package you're using.

Affected packages

Go/github.com/nats-io/nats-server/v2
Introduced in: 0Fixed in: 2.12.8
Fixgo get github.com/nats-io/nats-server/v2@v2.12.8
Go/github.com/nats-io/nats-server/v2
Introduced in: 2.14.0-RC.1Fixed in: 2.14.3
Fixgo get github.com/nats-io/nats-server/v2@v2.14.3

References