GHSA-f5v5-ccqc-6w36 TLS certificate common name validation bypass
A Man-in-the-Middle attacker can bypass TLS certificate validation in NATS Rust clients by tampering with the server's INFO message host field.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is GHSA-f5v5-ccqc-6w36?
GHSA-f5v5-ccqc-6w36 is a vulnerability in async-nats, published on 24 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
The NATS official Rust clients are vulnerable to MitM when using TLS.
The common name of the server's TLS certificate is validated against
the hostname provided by the server's plaintext INFO message
during the initial connection setup phase. A MitM proxy can tamper with
the host field's value by substituting it with the common name of a
valid certificate it controls, fooling the client into accepting it.
Reproduction steps
- The NATS Rust client tries to establish a new connection
- The connection is intercepted by a MitM proxy
- The proxy makes a separate connection to the NATS server
- The NATS server replies with an
INFOmessage - The proxy reads the
INFO, alters thehostJSON field and passes the tamperedINFOback to the client - The proxy upgrades the client connection to TLS, presenting a certificate issued
by a certificate authority present in the client's keychain.
In the previous step the
hostwas set to the common name of said certificate rustlsaccepts the certificate, having verified that the common name matches the attacker-controlled value it was given- The client has been fooled by the MitM proxy into accepting the attacker-controlled certificate
Which versions are affected by GHSA-f5v5-ccqc-6w36?
3 open source packages ship an affected version, including async-nats.
| Package | Affected | Fixed in |
|---|---|---|
async-nats crates.io | All versions | 0.29.0 |
async-nats crates.io | All versions | 0.29.0 |
async-nats crates.io | From 0.0.0-0 | 0.29.0 |
How do I fix GHSA-f5v5-ccqc-6w36?
Upgrade async-nats to 0.29.0 or later.
Is GHSA-f5v5-ccqc-6w36 being exploited?
There is no known exploitation of GHSA-f5v5-ccqc-6w36 in the wild and no public exploit code.
Sources
Also known as RUSTSEC-2023-0027.