Debian LinuxOperating system · Debian
CVE-2015-1782
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe kex_agree_methods function in libssh2 before 1.5.0 allows remote servers to cause a denial of service (crash) or have other unspecified impact via crafted length values in an SSH_MSG_KEXINIT packet.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA vulnerability in the kex_agree_methods function in libssh2 versions before 1.5.0 allows a remote malicious SSH server to cause a denial of service (crash) or potentially other unspecified impact by sending specially crafted length values within an SSH_MSG_KEXINIT packet during the key exchange phase.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Debian LinuxOperating system
= 7.0
FedoraOperating system
= 20= 21= 22<= 1.4.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed libssh2 versionQuery the package management system or inspect the libssh2 library binary to determine its precise version numberAffected if The version is 1.4.3 or lower, or matches the specific affected distribution versions (Debian 7.0, Fedora 20/21/22)
-
Confirm libssh2 is in useIdentify any applications or tools on the system that link against libssh2 and are used for SSH client connectionsAffected if SSH client applications or automation tools that utilize libssh2 are present and actively used
-
Check for untrusted SSH server connectionsReview SSH client configurations or scripts to determine if connections are made to external or untrusted SSH serversAffected if The system makes SSH connections to servers that are not fully trusted or are outside the organization's control
-
Verify key exchange occurs during connectionsConfirm that the SSH connections using libssh2 perform key exchange (this is standard for SSH protocol)Affected if The libssh2 library is used for connections that perform key exchange with remote servers
A user is affected if their installed libssh2 version is 1.4.3 or lower (or matches the listed affected distribution versions) AND the library is used to initiate SSH connections to remote servers, since the vulnerability is triggered during the key exchange phase by a malicious server.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade libssh2 to version 1.5.0 or later to patch the vulnerability. If upgrading is not immediately feasible, ensure SSH connections are only allowed to trusted servers.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1782 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-1782 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data