RUSTSEC-2023-0029

See a problem?
Please try reporting it to the source first.
Source
https://rustsec.org/advisories/RUSTSEC-2023-0029
Import Source
https://github.com/rustsec/advisory-db/blob/osv/crates/RUSTSEC-2023-0029.json
JSON Data
https://api.osv.dev/v1/vulns/RUSTSEC-2023-0029
Aliases
Published
2023-03-24T12:00:00Z
Modified
2023-11-08T09:57:41Z
Summary
TLS certificate common name validation bypass
Details

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

  1. The NATS Rust client tries to establish a new connection
  2. The connection is intercepted by a MitM proxy
  3. The proxy makes a separate connection to the NATS server
  4. The NATS server replies with an INFO message
  5. The proxy reads the INFO, alters the host JSON field and passes the tampered INFO back to the client
  6. 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 host was set to the common name of said certificate
  7. rustls accepts the certificate, having verified that the common name matches the attacker-controlled value it was given
  8. The client has been fooled by the MitM proxy into accepting the attacker-controlled certificate
Database specific 
{
    "license": "CC0-1.0"
}
References

Affected packages

crates.io / nats

Package

Name
nats
View open source insights on deps.dev
Purl
pkg:cargo/nats

Affected ranges

Type
SEMVER
Events
Introduced
0.9.0
Fixed
0.24.1

Ecosystem specific 

{
    "affected_functions": null,
    "affects": {
        "os": [],
        "functions": [],
        "arch": []
    }
}

Database specific 

{
    "cvss": null,
    "informational": null,
    "categories": [
        "crypto-failure"
    ]
}