CVE-2021-3634

MEDIUM
6.5
CVSS Score
Published: August 31, 2021 at 12:00 AM UTC
Updated: June 17, 2026 at 04:05 AM UTC
7 products affected across 6 vendorsDebian LinuxFedoraEnterprise Linux

Using libssh by N/A?

Get instant alerts when new vulnerabilities affect libssh - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.5
Exploit prediction
EPSS 5%

Description

A flaw has been found in libssh in versions prior to 0.9.6. The SSH protocol keeps track of two shared secrets during the lifetime of the session. One of them is called secret_hash and the other session_id. Initially, both of them are the same, but after key re-exchange, previous session_id is kept and used as an input to new secret_hash. Historically, both of these buffers had shared length variable, which worked as long as these buffers were same. But the key re-exchange operation can also change the key exchange method, which can be based on hash of different size, eventually creating "secret_hash" of different size than the session_id has. This becomes an issue when the session_id memory is zeroed or when it is used again during second key re-exchange.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

0.9.1 ≤ v < 0.9.60.9.6
Affected range stops below 0.9.6, so it looks safe — our inference, not a vendor statement
All versions

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-787

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card