CVE-2023-36933
Progress Moveit Transfer ≤ 2020.1.11
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HSummary
CVE-2023-36933 is a high-severity Improper Handling of Exceptional Conditions (CWE-755) vulnerability in Progress Moveit Transfer. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Client Execution (T1203); ranked in the top 0.6% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2023-36933 is an improper exception handling vulnerability in Progress MOVEit Transfer versions prior to 2021.0.9, 2021.1.7, 2022.0.7, 2022.1.8, and 2023.0.4. An unauthenticated remote attacker can invoke a specific method that triggers an unhandled exception, resulting in abrupt termination of the MOVEit Transfer application and a denial-of-service condition. The flaw carries a CVSS 3.1 base score of 7.5 reflecting network attack vector, low complexity, and high availability impact with no confidentiality or integrity consequences.
An attacker requires no credentials or user interaction and can trigger the condition simply by sending crafted requests to the affected service, causing the application to crash and interrupting file-transfer operations for legitimate users until the service is restarted.
Progress has released service packs that address the issue in the listed versions, and customers are advised to apply the updates referenced in the vendor’s July 2023 MOVEit Transfer advisory.
The associated EPSS score rose from a low baseline to a peak of 0.1915, indicating that exploitation interest increased after public disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-40853
Vulnerability Data
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…
more
application to terminate unexpectedly.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 1 hardening rule · 1 OS baseline
—
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Provides defined handling (alert and additional actions) for the exceptional condition of audit logging failure.
Supplies a concrete handling action (safe mode) for exceptional conditions, mitigating risks from improper or absent handling that could allow continued attacks.
By preparing users for contingency scenarios, the control promotes proper handling of exceptional conditions instead of default or unsafe behaviors.
An updated contingency plan defines current actions for exceptional conditions, reducing the window for attackers to exploit improper handling leading to system failure.
Procedures ensure proper handling of exceptional conditions to support effective incident response.
Incident response testing confirms proper handling of exceptional conditions to limit exploit impact.
Gives users guidance on incident handling, reducing improper handling of exceptional conditions that could stem from exploited weaknesses.
Enforces structured response to exceptional conditions so the system cannot remain in an unsafe state.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices explicitly require proper exception and error handling during design and coding.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development and acceptance verifies correct handling of exceptional conditions.
Documented operating procedures may specify exception handling but do not guarantee implementation.
Logging captures unhandled exceptions, aiding detection but not preventing the weakness.
Monitoring can surface unhandled exceptions but does not enforce proper handling.
Secure SDLC mandates exception-handling requirements and testing that directly prevent improper handling of exceptional conditions.
Application security requirements explicitly include handling of error and exceptional conditions.