CVE-2016-1907
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 ssh_packet_read_poll2 function in packet.c in OpenSSH before 7.1p2 allows remote attackers to cause a denial of service (out-of-bounds read and application crash) via crafted network traffic.
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 confidenceAn out-of-bounds read vulnerability exists in the ssh_packet_read_poll2 function in packet.c of OpenSSH versions prior to 7.1p2. The vulnerability is triggerable via crafted network traffic before authentication, allowing remote attackers to cause a denial of service by crashing the SSH daemon.
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= 6.8= 6.9= 7.0= 7.1CVSS 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- Low
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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.
-
Check the installed OpenSSH versionRun 'sshd -V' or 'ssh -V' to display the OpenSSH version. On Linux systems you can also use 'dpkg -l | grep openssh' or 'rpm -qa | grep openssh'. On FreeBSD use 'pkg_info | grep openssh'.Affected if The version displayed is 6.8, 6.9, 7.0, or 7.1, or any version prior to 7.1p2
-
Verify sshd is listening on a network portRun 'netstat -tlnp | grep ssh' or 'ss -tlnp | grep ssh' to see if the SSH daemon is bound to any network interfaces listening for incoming connections.Affected if sshd is bound to a network-accessible IP address on port 22 or another SSH port
-
Confirm the vulnerability trigger conditionThe flaw is triggered by crafted network packets sent to the SSH server before authentication completes. This requires no user credentials or special configuration to be exploitable.Affected if The sshd daemon accepts incoming network connections (which is the default behavior)
You are affected if your OpenSSH version is 6.8, 6.9, 7.0, or 7.1 (or any version prior to 7.1p2) and sshd is listening on a network-accessible port, allowing remote attackers to crash the daemon via crafted packets before authentication.
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 OpenSSH to version 7.1p2 or later to address this vulnerability. If immediate upgrade is not possible, consider restricting network access to SSH services via firewall rules to reduce attack surface.
- Consultation1.0 h
- Implementation2.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 $1,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1907 — 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-2016-1907 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