GSA_kwCzR0hTQS1qajU0LTVxMm0tcTdwas4AA8Ef

Low

Permalink JSON

NATS server TLS missing ciphersuite settings when CLI flags used

Affected Packages	Affected Versions	Fixed Versions
go:github.com/nats-io/nats-server/v2	< 2.2.3	2.2.3
6,417 Dependent packages 24,884 Dependent repositories Affected Version Ranges All affected versions 2.0.0, 2.0.2, 2.0.4, 2.1.0, 2.1.2, 2.1.4, 2.1.6, 2.1.7, 2.1.8, 2.1.9, 2.2.0, 2.2.1, 2.2.2 All unaffected versions 2.2.3, 2.2.4, 2.2.5, 2.2.6, 2.3.0, 2.3.1, 2.3.2, 2.3.3, 2.3.4, 2.4.0, 2.5.0, 2.6.0, 2.6.1, 2.6.2, 2.6.3, 2.6.4, 2.6.5, 2.6.6, 2.7.0, 2.7.1, 2.7.2, 2.7.3, 2.7.4, 2.8.0, 2.8.1, 2.8.2, 2.8.3, 2.8.4, 2.9.0, 2.9.1, 2.9.2, 2.9.3, 2.9.4, 2.9.5, 2.9.6, 2.9.7, 2.9.8, 2.9.9, 2.9.10, 2.9.11, 2.9.12, 2.9.14, 2.9.15, 2.9.16, 2.9.17, 2.9.18, 2.9.19, 2.9.20, 2.9.21, 2.9.22, 2.9.23, 2.9.24, 2.9.25, 2.10.0, 2.10.1, 2.10.2, 2.10.3, 2.10.4, 2.10.5, 2.10.6, 2.10.7, 2.10.8, 2.10.9, 2.10.10, 2.10.11, 2.10.12, 2.10.14, 2.10.15, 2.10.16, 2.10.17, 2.10.18, 2.10.19, 2.10.20, 2.10.21, 2.10.22, 2.10.23, 2.10.24, 2.10.25, 2.10.26, 2.10.27, 2.10.28, 2.10.29, 2.11.0, 2.11.1, 2.11.2, 2.11.3, 2.11.4, 2.11.5, 2.11.6

(This advisory is canonically https://advisories.nats.io/CVE/CVE-2021-32026.txt)

Problem Description

The NATS server by default uses a restricted set of modern ciphersuites for TLS. This selection can be overridden through configuration. The defaults include just RSA and ECDSA with either AES/GCM with a SHA2 digest or ChaCha20/Poly1305.

The configuration system allows for extensive use of CLI options to override configuration settings. When using these to set a key/cert for TLS, the restricted ciphersuite settings were lost, enabling all ciphersuites supported by Go by default.

None of these additional ciphersuites are broken, so the NATS maintainers have fixed this in public git and the next release is not being hurried, nor is this security advisory embargoed.

Affected versions

NATS Server:

All versions prior to 2.2.3
fixed with nats-io/nats-server commit ffccc2e1bd (2021-04-29)

Impact

If a server administrator chooses to start the nats-server with TLS configuration parameters provided on the command-line, then clients can negotiate TLS ciphersuites which were not expected.

Workaround

Use a configuration file to set the TLS parameters instead of command-line options.

Solution

Upgrade the NATS server.

Credits

This issue was identified and reported by SimCorp.

References:

ecosyste.ms

Data

Tools

Indexes

Applications

Experiments

Advisories

GSA_kwCzR0hTQS1qajU0LTVxMm0tcTdwas4AA8Ef

NATS server TLS missing ciphersuite settings when CLI flags used

Affected Version Ranges

All affected versions

All unaffected versions

Problem Description

Affected versions

Impact

Workaround

Solution

Credits

Identifiers

Risk

Severity

Classification

Source

Origin

Repository

Date and time

Published

Updated

API