Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

crates.io package

nats

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Unratedcrates.ioPublished

    NATS TLS certificate common name validation bypass

    GHSA-wvc4-j7g5-4f79

    Affected
    • crates.io nats >= 0.9.0, <= 0.24.0
    Fixed in
    0.24.1· Vendor fix available
    Issue
    The NATS official Rust clients are vulnerable to MitM when using TLS. A fix for the nats crate hasn't been released yet. Since the nats crate is going to be deprecated anyway, consider switching to async-nats = 0.29 which already fixed this vulnerability. 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…

    Recommended action: Upgrade to 0.24.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →