Overview
A critical cybersecurity vulnerability has been discovered that affects AllSky version v2023.05.01_04. Identified as CVE-2024-44373, it presents a severe Path Traversal vulnerability that could potentially be exploited by unauthenticated attackers to compromise systems or leak sensitive data. The vulnerability, due to the nature of its potential impact and the severity of the threat it poses, is a matter of high importance for organizations and individuals that use this version of AllSky.
Vulnerability Summary
CVE ID: CVE-2024-44373
Severity: Critical (9.8 CVSS score)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: Potential system compromise and data leakage
Affected Products
Escape the Surveillance Era
Most apps won’t tell you the truth.
They’re part of the problem.
Phone numbers. Emails. Profiles. Logs.
It’s all fuel for surveillance.
Ameeba Chat gives you a way out.
- • No phone number
- • No email
- • No personal info
- • Anonymous aliases
- • End-to-end encrypted
Chat without a trace.
Product | Affected Versions
AllSky | v2023.05.01_04
How the Exploit Works
The CVE-2024-44373 Path Traversal vulnerability exists in the save_file.php file in the /includes directory of AllSky. It allows an unauthenticated attacker to manipulate the path and content parameters to create a webshell. This webshell can subsequently be used for remote code execution, potentially granting the attacker full control over the targeted system.
Conceptual Example Code
A conceptual example of how this vulnerability might be exploited could look like a malicious HTTP POST request sent to the save_file.php endpoint. The attacker would manipulate the path and content parameters to create a webshell, as shown below:
POST /includes/save_file.php HTTP/1.1
Host: target.example.com
Content-Type: application/json
{
"path": "../../../../var/www/html/shell.php",
"content": "<?php echo shell_exec($_GET['cmd']); ?>"
}This example is highly simplified and conceptual. The actual exploitation process may vary based on the attacker’s tools, the specific configuration of the targeted system, and other factors.
Mitigation and Prevention
The best mitigation strategy for this vulnerability is to apply the vendor-provided patch as soon as it becomes available. If the patch is not available or cannot be applied immediately, temporary mitigation can be achieved by employing a Web Application Firewall (WAF) or an Intrusion Detection System (IDS) to detect and block exploitation attempts.
It is also recommended to monitor system logs for any unusual or suspicious activity, especially related to the /includes/save_file.php endpoint. Regularly updating and patching all software, as well as enforcing the principle of least privilege, can also help to limit the potential impact of this and other vulnerabilities.