Thursday, April 3, 2025
HomeCVE/vulnerabilityCrushFTP Vulnerability Lets Hackers Bypass Security and Seize Server Control

CrushFTP Vulnerability Lets Hackers Bypass Security and Seize Server Control

Published on

SIEM as a Service

Follow Us on Google News

A newly disclosed authentication bypass vulnerability (CVE-2025-2825) in CrushFTP file transfer software enables attackers to gain complete control of servers without valid credentials.

The vulnerability affects versions 10.0.0 through 11.3.0 of the popular enterprise file transfer solution, exposing organizations to data theft and system compromise.

The Exploit: Bypassing Security in 3 Steps

Security researchers have revealed how attackers can exploit this vulnerability using a simple HTTP request:

GET /WebInterface/function/?command=getUserList&c2f=1111 HTTP/1.1

Host: target-server:8081

Cookie: CrushAuth=1743113839553_vD96EZ70ONL6xAd1DAJhXMZYMn1111

Authorization: AWS4-HMAC-SHA256 Credential=crushadmin/

This attack combines three critical components:

  1. Spoofed AWS Header: Uses CrushFTP’s S3 protocol handling with a crushadmin username
  2. Fabricated Cookie: Requires a 44-character CrushAuth value with matching 4-digit code (1111 in this example)
  3. Parameter Manipulation: Leverages the c2f parameter to bypass password checks

The vulnerability stems from flawed authentication logic when processing S3-style requests:

  • System mistakes crushadmin/ credential as valid without password verification
  • Special cookie format tricks servers into accepting unauthenticated sessions
  • Attackers can then execute admin commands, including:
    • Downloading sensitive files
    • Creating new administrator accounts
    • Uploading malicious payloads

Security analysts confirm that 75% of CrushFTP instances remain unpatched as of March 31, 2025, despite fixes being available since March 26.

Detection and Mitigation

CrushFTP released version 11.3.1 with crucial fixes:

  • Disabled insecure S3 password lookup by default
  • Added security parameter s3_auth_lookup_password_supported=false
  • Implemented proper authentication flow checks

Immediate Action Required:

  1. Upgrade to CrushFTP ≥11.3.1 or ≥10.8.3
  2. Use ProjectDiscovery’s free detection tool:
nuclei -t https://cloud.projectdiscovery.io/public/CVE-2025-2825
  1. Audit server logs for suspicious GET requests to /WebInterface/function/

This vulnerability highlights three critical security lessons:

  1. Protocol Interaction Risks: Mixed authentication methods (S3 + cookies) create attack surfaces
  2. Default Configuration Dangers: Overly permissive defaults remain a systemic issue
  3. Response Time Gaps: 5-day patch adoption window leaves organizations exposed

Security teams should implement web application firewalls to block malformed S3 headers while patching. CrushFTP servers exposed to the internet should be considered high-risk until updated.

Find this News Interesting! Follow us on Google NewsLinkedIn, and X to Get Instant Updates!

Divya
Divya
Divya is a Senior Journalist at GBhackers covering Cyber Attacks, Threats, Breaches, Vulnerabilities and other happenings in the cyber world.

Latest articles

Qilin Operators Imitate ScreenConnect Login Page to Deploy Ransomware and Gain Admin Access

In a recent cyberattack attributed to the Qilin ransomware group, threat actors successfully compromised...

Operation HollowQuill Uses Malicious PDFs to Target Academic and Government Networks

A newly uncovered cyber-espionage campaign, dubbed Operation HollowQuill, has been identified as targeting academic,...

Cisco AnyConnect VPN Server Vulnerability Allows Attackers to Trigger DoS

Cisco has disclosed a significant vulnerability in its AnyConnect VPN Server for Meraki MX and Z...

New Trinda Malware Targets Android Devices by Replacing Phone Numbers During Calls

Kaspersky Lab has uncovered a new version of the Triada Trojan, a sophisticated malware...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

Qilin Operators Imitate ScreenConnect Login Page to Deploy Ransomware and Gain Admin Access

In a recent cyberattack attributed to the Qilin ransomware group, threat actors successfully compromised...

Operation HollowQuill Uses Malicious PDFs to Target Academic and Government Networks

A newly uncovered cyber-espionage campaign, dubbed Operation HollowQuill, has been identified as targeting academic,...

Cisco AnyConnect VPN Server Vulnerability Allows Attackers to Trigger DoS

Cisco has disclosed a significant vulnerability in its AnyConnect VPN Server for Meraki MX and Z...