LiveActive security incident?Get immediate response
CVE Record

CVE-2018-7750: transport.py in the SSH server implementation of Paramiko before 1.17.6, 1.18.x before 1.18.5, 2.0.x before...

transport.py in the SSH server implementation of Paramiko before 1.17.6, 1.18.x before 1.18.5, 2.0.x before 2.0.8, 2.1.x before 2.1.5, 2.2.x before 2.2.3, 2.3.x before 2.3.2, and 2.4.x before 2.4.1 does not properly check whether authentication is completed before processing other requests, as demonstrated by channel-open. A customized SSH client can simply skip the authentication step.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2018-7750 is an authentication bypass in Paramiko’s SSH server code. A specially customized SSH client could skip authentication and still trigger server-side request handling, such as opening a channel. This matters most for organizations running custom SSH services built on vulnerable Paramiko versions.

Executive priority

Treat this as high priority where Paramiko-backed SSH services are exposed or business-critical. The issue is older, but authentication bypass plus public exploit material makes unpatched reachable services unacceptable.

Technical view

Paramiko transport.py did not properly verify that authentication was complete before processing later SSH requests. The CVE identifies vulnerable branches before 1.17.6, 1.18.5, 2.0.8, 2.1.5, 2.2.3, 2.3.2, and 2.4.1. The public record points to an upstream issue, fix commit, and vendor package advisories.

Likely exposure

Exposure is most likely in Python applications or appliances that use Paramiko’s SSH server implementation, especially if reachable from untrusted networks. Systems using Paramiko only as an SSH client are not shown as affected in the provided sources.

Exploitation context

The source bundle includes an Exploit-DB reference, so public exploit material exists. CISA KEV is false in the bundle, and no provided source states active exploitation in the wild.

Researcher notes

The strongest evidence is the CVE description, upstream issue, upstream commit, and multiple Linux vendor advisories. Severity scoring and CWE data are absent in the supplied bundle, so impact should be validated against the specific server implementation and authorization model.

Mitigation direction

  • Upgrade Paramiko beyond the vulnerable versions listed in the CVE record.
  • Apply relevant Red Hat, Ubuntu, or Debian package security updates.
  • Restrict network access to affected SSH server endpoints.
  • Audit custom services that embed Paramiko server functionality.
  • Monitor vendor advisories for environment-specific remediation details.

Validation and detection

  • Inventory Python dependencies and OS packages for Paramiko versions.
  • Identify services using Paramiko as an SSH server, not only as a client.
  • Confirm deployed versions meet or exceed the fixed branch versions.
  • Review exposure of affected SSH endpoints to untrusted networks.
  • Check logs for unauthenticated request or channel activity.
Prepared
Confidence
medium
Sources
10

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2018-7750 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
18Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.