Moveit TransferApplication · Ipswitch

CVE-2019-18465

CRITICAL · 9.8 CVSS v3.1 Published 2019-10-31
Fix available
A fix is available. Upgrade to 11.1.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
In Progress MOVEit Transfer 11.1 before 11.1.3, a vulnerability has been found that could allow an attacker to sign in without full credentials via the SSH (SFTP) interface. The vulnerability affects only certain SSH (SFTP) configurations, and is applicable only if the MySQL database is being used.

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 confidence

This is an authentication bypass vulnerability in Progress MOVEit Transfer SFTP/SSH interface. Attackers can sign in without full credentials by exploiting a flaw in the authentication logic specific to MySQL database configurations. The vulnerability exists in versions 11.1 through 11.1.2 and is patched in version 11.1.3.

MitigationUpgrade MOVEit Transfer to version 11.1.3 or later. Organizations using MySQL with SFTP should prioritize this patch given the critical CVSS score and the authentication bypass nature of the flaw.

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
Moveit TransferApplication
Affected:>= 11.1, < 11.1.3

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
High

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify MOVEit Transfer installation
    Locate the MOVEit Transfer installation directory or check for the MOVEit Transfer service on the system.
    Affected if MOVEit Transfer software is present on the system.
  2. Determine installed version
    Check the MOVEit Transfer version information through the administration interface, installed program details, or version file within the application directory.
    Affected if The installed version is 11.1, 11.1.1, or 11.1.2 (any version from 11.1 up to but not including 11.1.3).
  3. Verify SFTP/SSH module is enabled
    Check the MOVEit Transfer configuration to confirm the SFTP/SSH interface is enabled and accessible.
    Affected if The SFTP/SSH interface is active and exposed for user authentication.
  4. Confirm database type
    Review the MOVEit Transfer database configuration to identify whether MySQL is used as the backend database.
    Affected if MySQL is configured as the database backend for MOVEit Transfer.

A user is affected if MOVEit Transfer version is between 11.1 and 11.1.2 inclusive, the SFTP/SSH interface is enabled, and MySQL is used as the database backend.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 11.1.3 or later
Fixed in 11.1.3
Interim mitigation

Upgrade MOVEit Transfer to version 11.1.3 or later. Organizations using MySQL with SFTP should prioritize this patch given the critical CVSS score and the authentication bypass nature of the flaw.

Recommended fix High confidence

Moveit Transfer 11.1.3 or later

  1. 1. Backup the current Moveit Transfer installation and database before proceeding with any upgrade.
  2. 2. Verify the current installed version matches the affected range (>= 11.1, < 11.1.3).
  3. 3. Confirm that the MySQL database is in use and SSH/SFTP configuration is enabled, as these conditions are required for the vulnerability.
  4. 4. Download Moveit Transfer version 11.1.3 or later from the official Ipswitch customer portal or authorized distribution channel.
  5. 5. Install the upgrade following the standard Moveit Transfer upgrade procedure documented in docs.ipswitch.com.
  6. 6. After upgrade, verify the SSH/SFTP authentication functions correctly with proper credentials.
  7. 7. Review authentication logs to confirm the fix is operational and no unauthorized access attempts are occurring.
Caveat Review upgrade documentation for any configuration changes required between 11.1.x and 11.1.3; test in non-production environment first

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

Fix this in Moveit Transfer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-18465 — 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-2019-18465 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