LiveActive security incident?Get immediate response
CVE Record

CVE-2022-38337: When aborting a SFTP connection, MobaXterm before v22.1 sends a hardcoded password to the server.

When aborting a SFTP connection, MobaXterm before v22.1 sends a hardcoded password to the server. The server treats this as an invalid login attempt which can result in a Denial of Service (DoS) for the user if services like fail2ban are used.

CriticalCVSS 9.1Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

MobaXterm versions before v22.1 can send a hardcoded password to an SFTP server when a user aborts a connection. The server may record this as a failed login, which can lock out the user or trigger denial-of-service effects when tools such as fail2ban are active.

Executive priority

Treat this as a focused endpoint-client remediation issue, not a broad server compromise claim. The business risk is disruption to SFTP access and possible exposure from a hardcoded credential behavior in legacy clients.

Technical view

The reported issue is CWE-798: hardcoded credentials. During SFTP abort handling, affected MobaXterm clients send a fixed password to the server. Source metadata assigns CVSS 3.1 score 9.1 with network attack vector, no privileges, no user interaction, high confidentiality impact, and high availability impact.

Likely exposure

Exposure is likely limited to environments where users run MobaXterm before v22.1 for SFTP, especially against servers enforcing failed-login lockouts or automated blocking. The source bundle does not provide CPEs, platform details, or enterprise prevalence data.

Exploitation context

The bundle does not show CISA KEV inclusion or cite active exploitation. The described impact can occur from the client behavior during aborted SFTP sessions, with downstream lockout or blocking effects on the server side.

Researcher notes

Evidence supports affected MobaXterm before v22.1 and a hardcoded password sent during SFTP abort handling. The source bundle lacks detailed vulnerable build ranges, proof of exploitation, CPE mappings, and vendor advisory text beyond the referenced download page.

Mitigation direction

  • Inventory MobaXterm installations and identify versions before v22.1.
  • Prioritize upgrading affected clients to v22.1 or later.
  • Check current Mobatek guidance before standardizing remediation steps.
  • Review fail2ban and lockout policies for affected SFTP services.
  • Warn users to report unexpected SFTP lockouts during remediation.

Validation and detection

  • Confirm installed MobaXterm versions on managed endpoints.
  • Review SFTP authentication logs for invalid attempts linked to aborted sessions.
  • Check fail2ban or equivalent logs for user or IP blocks.
  • Verify upgraded clients no longer match the affected version range.
Prepared
Confidence
medium
Sources
4

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.

cwe · medium confidence lookup

CWE-798: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-38337 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
Critical
CVSS
9.1 (3.1)
Known Exploited
No
Published

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

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H3.95.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.1Critical
CVSS 3.1 vector shape for CVE-2022-38337Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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

CWE-798 · source CWE mapping

Use of Hard-coded Credentials

Use of Hard-coded Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.