Ubuntu LinuxOperating system · Canonical

CVE-2018-10933

CRITICAL · 9.1 CVSS v3.0 Published 2018-10-17
Fix available
A fix is available. Upgrade to 0.7.6 / 0.8.4 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Public exploit Remotely reachable No privileges Zero-click Patch available

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 · unedited
A vulnerability was found in libssh's server-side state machine before versions 0.7.6 and 0.8.4. A malicious client could create channels without first performing authentication, resulting in unauthorized access.

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

A detailed technical summary for this CVE is being prepared.

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
Ubuntu LinuxOperating system
Affected:= 14.04= 16.04= 18.04= 18.10
Debian LinuxOperating system
Affected:= 8.0= 9.0
Enterprise LinuxOperating system
Affected:= 7.0
LibsshApplication
Affected:>= 0.6.0, < 0.7.6>= 0.8.0, < 0.8.4
Oncommand Unified ManagerApplication
Affected:>= 7.3>= 9.4
Oncommand Workflow AutomationApplication
Affected:all versions
SnapcenterApplication
Affected:all versions
Storage Automation StoreApplication
Affected:all versions

CVSS 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
High
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

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.

dbcve · scoped
Upgrade available Upgrade to 0.7.6 / 0.8.4 or later
Fixed in 0.7.60.8.4
Vendor patch www.oracle.com →
Recommended fix High confidence

libssh 0.7.6 or 0.8.4 (or later stable release)

  1. Identify the vulnerable libssh package or dependent product in your environment
  2. Check the current installed version of libssh (e.g., dpkg -l libssh-* or rpm -qa | grep libssh)
  3. Upgrade to libssh version 0.7.6, 0.8.4, or a later stable release using your package manager (apt-get update && apt-get install libssh-4 or yum update libssh)
  4. For embedded products (Oncommand Unified Manager, Oncommand Workflow Automation, Snapcenter, Storage Automation Store), apply vendor-specific patches from the Oracle Security Advisory cpujan2019-5072801
  5. Restart any SSH services or applications that use libssh to load the updated library
  6. Verify the installed version matches the fixed release (>= 0.7.6 or >= 0.8.4)
Caveat Upgrading libssh may require restarting services; ensure compatibility with dependent applications before upgrading in production environments

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-10933 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-10933 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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