dbcve.org
Moveit TransferApplication · Progress

CVE-2024-0396

HIGH · 7.1 CVSS v3.1 Published 2024-01-17
Fix available
A fix is available. Upgrade to 2022.0.10 / 2022.1.11 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable 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 versions released before 2022.0.10 (14.0.10), 2022.1.11 (14.1.11), 2023.0.8 (15.0.8), 2023.1.3 (15.1.3), an input validation issue was discovered. An authenticated user can manipulate a parameter in an HTTPS transaction. The modified transaction could lead to computational errors within MOVEit Transfer and potentially result in a denial of service.

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

An authenticated user can manipulate a parameter in an HTTPS transaction within MOVEit Transfer, causing computational errors and potential denial of service. The vulnerability stems from insufficient input validation on user-controlled parameters.

MitigationApply the vendor-supplied patch by upgrading MOVEit Transfer to version 2022.0.10 (14.0.10), 2022.1.11 (14.1.11), 2023.0.8 (15.0.8), or 2023.1.3 (15.1.3) or later, depending on the current branch.

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:< 2022.0.10>= 2022.1.0, < 2022.1.11>= 2023.0.1, < 2023.0.8>= 2023.1.0, < 2023.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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. Confirm MOVEit Transfer installation
    Locate the MOVEit Transfer installation directory (commonly C:\Program Files\Progress\MOVEit Transfer or /opt/moveit/transfer) or check for the MOVEit Transfer Windows service. On Windows, run: Get-Service | Where-Object {$_.Name -like '*MOVEit*'}. On Linux, run: ps aux | grep -i moveit
    Affected if MOVEit Transfer is not installed or not running
  2. Determine installed version
    Check the installed version via the admin interface (Help > About in MOVEit Transfer Admin), or inspect the version file in the installation directory. On Windows, the version may be visible in Programs and Features. On Linux, check /opt/moveit/transfer/ or the installed package version.
    Affected if The installed version falls within any of these ranges: < 2022.0.10; >= 2022.1.0 and < 2022.1.11; >= 2023.0.1 and < 2023.0.8; >= 2023.1.0 and < 2023.1.3
  3. Verify HTTPS web interface is enabled
    Confirm the MOVEit Transfer web interface is accessible via HTTPS. The vulnerability exploits insufficient input validation on user-controlled parameters within HTTPS transactions. Check if port 443 (or configured HTTPS port) is listening and the web application responds.
    Affected if The HTTPS web interface is enabled and accessible, as this is the attack vector for the vulnerable parameter handling
  4. Confirm user authentication is configured
    Verify that MOVEit Transfer has user authentication enabled (local users, AD integration, or other authentication methods). The CVEs description specifies an authenticated user is required to exploit this flaw.
    Affected if User authentication is enabled, as exploitation requires an authenticated session

A system is affected if MOVEit Transfer is installed with a version matching the vulnerable ranges AND the HTTPS web interface is enabled, allowing authenticated users to send manipulated HTTPS requests.

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 2022.0.10 / 2022.1.11 / 2023.0.8 or later
Fixed in 2022.0.102022.1.112023.0.8
Interim mitigation

Apply the vendor-supplied patch by upgrading MOVEit Transfer to version 2022.0.10 (14.0.10), 2022.1.11 (14.1.11), 2023.0.8 (15.0.8), or 2023.1.3 (15.1.3) or later, depending on the current branch.

Recommended fix High confidence

Upgrade to 2022.0.10, 2022.1.11, 2023.0.8, or 2023.1.3 depending on your current version branch

  1. 1. Identify the currently installed MOVEit Transfer version by checking the application's about page or version information.
  2. 2. Determine which version branch you are running (2022.0.x, 2022.1.x, 2023.0.x, or 2023.1.x).
  3. 3. For version 2022.0.x: Upgrade to version 2022.0.10 (14.0.10) or later.
  4. 4. For version 2022.1.x: Upgrade to version 2022.1.11 (14.1.11) or later.
  5. 5. For version 2023.0.x: Upgrade to version 2023.0.8 (15.0.8) or later.
  6. 6. For version 2023.1.x: Upgrade to version 2023.1.3 (15.1.3) or later.
  7. 7. Download the appropriate installer from the Progress Customer Portal or official download channels.
  8. 8. Before upgrading, backup the MOVEit Transfer configuration and database.
Caveat Standard upgrade considerations apply - review release notes for your specific version path for any behavior changes

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
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.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-2024-0396 — 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-0396 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