dbcve.org
Moveit TransferApplication · Progress

CVE-2024-5806

CRITICAL · 9.8 CVSS v3.1 Published 2024-06-25
Fix available
A fix is available. Upgrade to 2023.0.11 / 2023.1.6 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS 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
Improper Authentication vulnerability in Progress MOVEit Transfer (SFTP module) can lead to Authentication Bypass.This issue affects MOVEit Transfer: from 2023.0.0 before 2023.0.11, from 2023.1.0 before 2023.1.6, from 2024.0.0 before 2024.0.2.

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

Improper authentication in the SFTP module of Progress MOVEit Transfer allows attackers to bypass authentication mechanisms entirely. This critical flaw affects specific version ranges (2023.0.0-2023.0.10, 2023.1.0-2023.1.5, and 2024.0.0-2024.0.1), enabling unauthenticated remote access to the file transfer service.

MitigationUpgrade MOVEit Transfer to version 2023.0.11, 2023.1.6, or 2024.0.2 or later to resolve the authentication bypass in the SFTP module. Schedule during maintenance window and validate SFTP functionality post-upgrade.

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:>= 2023.0.0, < 2023.0.11>= 2023.1.0, < 2023.1.6= 2024.0.0

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 version
    Check the installed version via the MOVEit Transfer admin interface under System > About, or query the Windows registry key HKLM\SOFTWARE\Progress\MOVEitTransfer\CurrentVersion
    Affected if The version displayed is 2023.0.0-2023.0.10, 2023.1.0-2023.1.5, or exactly 2024.0.0
  2. Verify SFTP module is enabled
    Navigate to the MOVEit Transfer admin console and check System > Services > SFTP or look for SFTP-related configuration under the Hosts settings
    Affected if SFTP service is listed as running or enabled
  3. Confirm SFTP is exposed externally
    Review network configuration to determine if the SFTP port (typically port 22 or configured custom port) is accessible from external networks, or check firewall rules for inbound SFTP connections
    Affected if SFTP port is reachable from untrusted networks or the internet
  4. Check authentication configuration
    In the admin interface under SFTP settings, verify if anonymous or password-less authentication is permitted, or inspect the SFTP configuration files in the MOVEit installation directory
    Affected if No enforced authentication or weak auth settings are configured for the SFTP module

You are affected if MOVEit Transfer version falls within 2023.0.0-2023.0.10, 2023.1.0-2023.1.5, or 2024.0.0 AND the SFTP module is enabled and accessible.

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 2023.0.11 / 2023.1.6 or later
Fixed in 2023.0.112023.1.6
Interim mitigation

Upgrade MOVEit Transfer to version 2023.0.11, 2023.1.6, or 2024.0.2 or later to resolve the authentication bypass in the SFTP module. Schedule during maintenance window and validate SFTP functionality post-upgrade.

Recommended fix High confidence

MOVEit Transfer 2023.0.11, 2023.1.6, or 2024.0.2 (depending on your current branch)

  1. 1. Identify the currently installed MOVEit Transfer version by checking the application or configuration.
  2. 2. For versions 2023.0.0 through 2023.0.10: Upgrade to version 2023.0.11 or later.
  3. 3. For versions 2023.1.0 through 2023.1.5: Upgrade to version 2023.1.6 or later.
  4. 4. For version 2024.0.0: Upgrade to version 2024.0.2 or later.
  5. 5. After upgrading, verify the SFTP module is functioning correctly and review audit logs for any suspicious authentication attempts that may have occurred prior to patching.
Caveat Review Progress release notes for your specific version upgrade path for any compatibility or configuration changes

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

Fix this in Moveit Transfer Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-5806 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2024-5806 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