InfoSecBulletin Cybersecurity for mankind
SonicWall Capture Labs found a vulnerability with the Artica Proxy appliance. This vulnerability affects over 100K servers globally. Artica Proxy is a proxy solution that performs tasks like web filtering, SSL inspection, and bandwidth management. SonicWall has developed measures to mitigate the vulnerability.
There is a security vulnerability called CVE-2024-2054 in the administrative web interface. It allows users to execute code without authentication, which can lead to the execution of code under the “www-data” user account. The severity score is 9.8. This affects version 4.50 and earlier versions. Although there are currently no reports of active attacks, there is a publicly available proof of concept provided by the Korelogic research team.
CVSS 9.6: IBM QRadar & Cloud Pak Security Flaws Exposed
ALERT
Thousands of IP addresses compromised nationwide: CIRT warn
New Android Malware ‘Crocodilus’ Targets Banks in 8 Countries
Qualcomm Patches 3 Zero-Days Used in Targeted Android Attacks
Critical RCE Flaw Patched in Roundcube Webmail
Hacker claim Leak of Deloitte Source Code & GitHub Credentials
CISA Issued Guidance for SIEM and SOAR Implementation
Linux flaws enable password hash theft via core dumps in Ubuntu, RHEL, Fedora
Australia enacts mandatory ransomware payment reporting
Why Govt Demands Foreign CCTV Firms to Submit Source Code?
The vendor has not released a patch yet. Organizations are strongly advised to follow the steps in the mitigation section below. SonicWall customers are already protected with IPS signature 19786, released on March 18th.
Technical Overview:
An unauthenticated user can send an HTTP POST request to the “/wizard/wiz.wizard.progress.php” endpoint with the “build-js” query parameter.
During the “build-js” user input processing, it decodes the base64 value and sends it to the “unserialize” PHP function. This is depicted in Figure 2.
This is the root cause of the vulnerability, as an unauthenticated attacker can control the base64 encoded input which is then directly deserialized.
Triggering the Vulnerability:
To exploit this vulnerability, an attacker needs to send an HTTP POST request to the Artica Proxy instance with the manipulated “build-js” parameter set to a base64-encoded payload. The public PoC code demonstrates this using the Linux “curl” command as shown in Figure 3.
to read the full report click here.
