CVE-2024-2054 in the critical feed json
Artica Proxy Unauthenticated PHP Deserialization Vulnerability
published 2024-03-05 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-27019
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 81.3%
- EPSS 81.3% chance of exploitation in 30 days, percentile 99.6%
- public exploits
- 2
- Metasploit, Exploit-DB
Summary
The Artica-Proxy administrative web application will deserialize arbitrary PHP objects supplied by unauthenticated users and subsequently enable code execution as the "www-data" user.
Timeline
- First public exploit (Metasploit exploit/linux/http/artica_proxy_unauth_rce_cve_2024_2054)
- Published
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- total
- Assessed
- 2 y ago
Exploit prediction
81.26% chance of exploitation in the next 30 days, higher than 99.6% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Metasploit exploit/linux/http/artica_proxy_unauth_rce_cve_2024_2054 Artica Proxy Unauthenticated PHP Deserialization Vulnerability metasploit exploit, excellent rank, 2024-03-05
- EDB-52146 Artica Proxy 4.50 - Remote Code Execution (RCE) webapps, 2025-04-09
- korelogic.com https://korelogic.com/Resources/Advisories/KL-001-2024-002.txt referenced PoC, tagged "exploit" by a source, unverified
- seclists.org http://seclists.org/fulldisclosure/2024/Mar/12 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Artica Tech Artica Proxy
- articatech artica_proxy
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
References
-
korelogic.com
/Resources/Advisories/KL-001-2024-002.txt
third-party-advisory, exploit
-
seclists.org
/fulldisclosure/2024/Mar/12
exploit, mailing-list
Sources
- CVE List CVE-2024-2054
- NVD CVE-2024-2054
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.