CRITICAL · CVSS 9.8 CISA Known Exploited Vulnerability Used in ransomware attacks

CVE-2023-34362

Progress MOVEit Transfer SQL Injection Vulnerability

Progress MOVEit Transfer

In Progress MOVEit Transfer before 2021.0.6 (13.0.6), 2021.1.4 (13.1.4), 2022.0.4 (14.0.4), 2022.1.5 (14.1.5), and 2023.0.1 (15.0.1), a SQL injection vulnerability has been found in the MOVEit Transfer web application that could allow an unauthenticated attacker to gain access to MOVEit Transfer's database. Depending on the database engine being used (MySQL, Microsoft SQL Server, or Azure SQL), an attacker may be able to infer information about the structure and contents of the database, and execute SQL statements that alter or delete database elements. NOTE: this is exploited in the wild in May and June 2023; exploitation of unpatched systems can occur via HTTP or HTTPS. All versions (e.g., 2020.0 and 2019x) before the five explicitly mentioned versions are affected, including older unsupported versions.

CVSS
9.8
CRITICAL
EPSS
99.9%
30-day exploitation
Ransomware groups
1
recorded exploiting
Published
2 Jun 2023
CWE-89

Ransomware groups exploiting CVE-2023-34362

Clop 783 victims tracked

The ransomware group known as Cl0p is a variant of a previously known strain dubbed CryptoMix. It is worth noting that this variant was delivered as the final payload in a phishing campaign in 2019 and was exclusively financially motivated, with attacks carrie

Exploitation is attributed to these groups across their recorded activity. It does not follow that every organisation they listed was reached through CVE-2023-34362 — the source data does not record an entry point per incident.

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 2 June 2023. US federal agencies were required to remediate it by 23 June 2023. CISA records this vulnerability as known to be used in ransomware campaigns.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 99.9%, which is higher than 99.9% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

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

Recent listings by these groups

Disclosures from the groups above, newest first.

Frequently asked questions

Is CVE-2023-34362 being exploited by ransomware groups?

Yes. CVE-2023-34362 is recorded as exploited by Clop. Between them these groups account for 783 victim disclosures in this database. CISA also records this vulnerability as used in ransomware campaigns.

What does CVE-2023-34362 affect?

CVE-2023-34362 affects Progress MOVEit Transfer. In Progress MOVEit Transfer before 2021.0.6 (13.0.6), 2021.1.4 (13.1.4), 2022.0.4 (14.0.4), 2022.1.5 (14.1.5), and 2023.0.1 (15.0.1), a SQL injection vulnerability has been found in the MOVEit Transfer web application that could allow an unauthenticated attacker to gain access to MOVEit Transfer's database. Depending on the database engine being used (MySQL, Microsoft SQL Server, or Azure SQL), an attacker may be able to infer information about the structure and contents of the database, and execute SQL statements that alter or delete database elements. NOTE: this is exploited in the wild in May and June 2023; exploitation of unpatched systems can occur via HTTP or HTTPS. All versions (e.g., 2020.0 and 2019x) before the five explicitly mentioned versions are affected, including older unsupported versions.

How severe is CVE-2023-34362?

CVE-2023-34362 is rated CRITICAL with a CVSS base score of 9.8. EPSS puts the probability of exploitation in the next 30 days at 99.9%, higher than 99.9% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 23 June 2023.

How should organisations respond to CVE-2023-34362?

Apply the vendor patch for Progress MOVEit Transfer as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.