dbcve.org
Moveit TransferApplication · Progress

CVE-2023-36933

HIGH · 7.5 CVSS v3.1 Published 2023-07-05
Fix available
A fix is available. Upgrade to 2020.1.11 / 2021.0.9 or later.
See remediation →
84/100
Remediation priority · High
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
In Progress MOVEit Transfer before 2021.0.9 (13.0.9), 2021.1.7 (13.1.7), 2022.0.7 (14.0.7), 2022.1.8 (14.1.8), and 2023.0.4 (15.0.4), it is possible for an attacker to invoke a method that results in an unhandled exception. Triggering this workflow can cause the MOVEit Transfer application to terminate unexpectedly.

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 · moderate confidence

A denial of service vulnerability exists in Progress MOVEit Transfer where an unauthenticated attacker can invoke a specific method that triggers an unhandled exception, causing the application to terminate unexpectedly. The vulnerability affects multiple version branches (2021.x, 2022.x, 2023.x) prior to the specified patched releases.

MitigationApply the available vendor patches for all affected MOVEit Transfer versions (2021.0.9, 2021.1.7, 2022.0.7, 2022.1.8, and 2023.0.4 or later) to remediate the unhandled exception vulnerability.

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:< 2020.1.11>= 2021.0, < 2021.0.9>= 2021.1.0, < 2021.1.7>= 2022.0.0, < 2022.0.7>= 2022.1.0, < 2022.1.8>= 2023.0.0, < 2023.0.4

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 installed version
    Locate the installed version through the application admin interface, installation logs, or product documentation. The version is typically visible in the web UI footer or in the program's about/details section.
    Affected if The installed version falls within the affected ranges: < 2020.1.11, >= 2021.0.0 to < 2021.0.9, >= 2021.1.0 to < 2021.1.7, >= 2022.0.0 to < 2022.0.7, >= 2022.1.0 to < 2022.1.8, or >= 2023.0.0 to < 2023.0.4
  2. Confirm MOVEit Transfer web interface is accessible
    Verify the MOVEit Transfer web portal is reachable on the configured port (typically ports 80, 443, or custom ports as configured during installation).
    Affected if The web interface is exposed to network traffic, as the vulnerability is exploitable by an unauthenticated remote attacker
  3. Determine if the specific SFTP/API endpoint is exposed
    Check whether the MOVEit Transfer SFTP or API services are accessible from untrusted networks, as the vulnerability involves invoking a specific method that triggers the unhandled exception.
    Affected if The application endpoint accepting unauthenticated requests is reachable from external or untrusted networks

The environment is affected if MOVEit Transfer version is one of the unpatched versions listed in the affected ranges AND the web/API interface is network-accessible to potential attackers.

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 2020.1.11 / 2021.0.9 / 2021.1.7 or later
Fixed in 2020.1.112021.0.92021.1.7
Interim mitigation

Apply the available vendor patches for all affected MOVEit Transfer versions (2021.0.9, 2021.1.7, 2022.0.7, 2022.1.8, and 2023.0.4 or later) to remediate the unhandled exception vulnerability.

Recommended fix High confidence

2023.0.4 (15.0.4) or the latest available version

  1. 1. Identify the currently installed MOVEit Transfer version by checking the application or system information
  2. 2. Based on the current version, determine the appropriate upgrade path to a fixed release
  3. 3. For versions 2020.1.x: upgrade to 2020.1.11 or later
  4. 4. For versions 2021.0.x: upgrade to 2021.0.9 or later
  5. 5. For versions 2021.1.x: upgrade to 2021.1.7 or later
  6. 6. For versions 2022.0.x: upgrade to 2022.0.7 or later
  7. 7. For versions 2022.1.x: upgrade to 2022.1.8 or later
  8. 8. For versions 2023.0.x: upgrade to 2023.0.4 or later
Caveat Review Release Notes for any configuration or behavioral changes between versions; 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 / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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