NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Go

CVE-2021-32026: NATS server TLS missing ciphersuite settings when CLI flags used

lowGHSA-jj54-5q2m-q7pj

(This advisory is canonically ) 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.

Published May 14, 2024 · Updated May 21, 2024

Affected packages

github.com/nats-io/nats-server/v2

Ecosystem
Go
Affected
< 2.2.3
Fixed in
2.2.3
Check
go list -m github.com/nats-io/nats-server/v2

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

(This advisory is canonically )

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.

Credited to lukas-braune.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More Go vulnerabilities

All Go entries