Advisories
This weekExploitable · Confirmed

russh, golang.org/x/crypto: Prefix Truncation Attack against ChaCha20-Poly1305 and Encrypt-then-MAC aka Terrapin

There is evidence it can be used, or an emergency alert, without the proof that makes it urgent.

Does it affect what I run?

Checked in your browser. The version you type is not sent anywhere.

Who is affected

  • russh (crates.io): every version, before 0.40.2
  • golang.org/x/crypto (Go): from 0.1.0, before 0.17.0
  • paramiko (PyPI): from 2.5.0, before 3.4.0
  • golang.org/x/crypto (Go): every version, before 0.0.0-20231218163308-9d2ee975ef9f
  • paramiko (PyPI): from 2.5.0, before 3.4.0
  • golang.org/x/crypto (Go): every version, before 0.17.0

The fix

  • russh (crates.io) fixed in 0.40.2

    cargo
    cargo update -p russh --precise 0.40.2
    Check what is installed
    cargo tree -i russh
    Paste into Cursor, Lovable or Claude Code
    Upgrade the crates.io dependency russh to 0.40.2 or the nearest later release, to fix CVE-2023-48795. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • golang.org/x/crypto (Go) fixed in 0.17.0

    go
    go get golang.org/x/crypto@v0.17.0
    Check what is installed
    go list -m golang.org/x/crypto
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Go dependency golang.org/x/crypto to 0.17.0 or the nearest later release, to fix CVE-2023-48795. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • golang.org/x/crypto (Go) fixed in 0.0.0-20231218163308-9d2ee975ef9f

    go
    go get golang.org/x/crypto@v0.0.0-20231218163308-9d2ee975ef9f
    Check what is installed
    go list -m golang.org/x/crypto
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Go dependency golang.org/x/crypto to 0.0.0-20231218163308-9d2ee975ef9f or the nearest later release, to fix CVE-2023-48795. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • paramiko (PyPI) fixed in 3.4.0

    pip
    python -m pip install paramiko==3.4.0
    uv
    uv add paramiko==3.4.0
    poetry
    poetry add paramiko@3.4.0
    Check what is installed
    python -m pip show paramiko
    Paste into Cursor, Lovable or Claude Code
    Upgrade the PyPI dependency paramiko to 3.4.0 or the nearest later release, to fix CVE-2023-48795. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.

Fix commands generated from the advisory's versions. No model wrote them.

In plain words

Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.

Evidence

Timeline

  1. First published here, as "For your digest".
  2. Level changed from "For your digest" to "This week".
  3. Evidence added: EPSS rates exploitation in the next 30 days as more likely than not. (FIRST EPSS)
  4. Evidence added: CISA's assessment in the CVE record says a proof of concept is public. (CISA Vulnrichment (SSVC and KEV fields inside CVE records))