CrushFTP · CrushFTP · CWE-305 · published 2025-04-03

CVE-2025-31161CrushFTP Authentication Bypass Vulnerability

Patch today Known exploited and used in ransomware campaigns.

CVE-2025-31161 is actively exploited in the wild: CISA added it to the Known Exploited Vulnerabilities catalog on 2025-04-07, and it is known to be used in ransomware campaigns. EPSS estimates a 100% chance of exploitation in the next 30 days, higher than 99% of all CVEs. This CrushFTP vulnerability: CVSS 9.8 (v3.1), attacks can be automated, a successful attack gives total control of the component. CISA’s required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. US federal agencies must remediate by 2025-04-28. Patch today.

Share this

Remediation#

CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. (federal due date 2025-04-28)

Patch events

  1. Patch todayExploited (KEV)CISA due 2025-04-28

    File transferCrushFTP

    Authentication BypassCVE-2025-31161

    Why: Known exploited and used in ransomware campaigns.

Exploit intelligence#

SignalValueSource
Known exploitedYes, added 2025-04-07CISA KEV
Ransomware useKnownCISA KEV
EPSS (30-day exploitation probability)100% (100th pct)FIRST EPSS v2026.06.15
CVSS base score9.8 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA / CISA ADP
SSVC exploitationactiveCISA Vulnrichment
SSVC automatableYesCISA Vulnrichment
SSVC technical impacttotalCISA Vulnrichment

Weakness: CWE-305: Authentication Bypass by Primary Weakness

More from this vendor: all CrushFTP vulnerabilities · recent KEV additions

Affected versions (from the CVE record)#

Description (from the CVE record)#

CrushFTP 10 before 10.8.4 and 11 before 11.3.1 allows authentication bypass and takeover of the crushadmin account (unless a DMZ proxy instance is used), as exploited in the wild in March and April 2025, aka "Unauthenticated HTTP(S) port access." A race condition exists in the AWS4-HMAC (compatible with S3) authorization method of the HTTP component of the FTP server. The server first verifies the existence of the user by performing a call to login_user_pass() with no password requirement. This will authenticate the session through the HMAC verification process and up until the server checks for user verification once more. The vulnerability can be further stabilized, eliminating the need for successfully triggering a race condition, by sending a mangled AWS4-HMAC header. By providing only the username and a following slash (/), the server will successfully find a username, which triggers the successful anypass authentication process, but the server will fail to find the expected SignedHeaders entry, resulting in an index-out-of-bounds error that stops the code from reaching the session cleanup. Together, these issues make it trivial to authenticate as any known or guessable user (e.g., crushadmin), and can lead to a full compromise of the system by obtaining an administrative account.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →