timber/timber
Affected
- introduced
2.0.0, fixed2.1.0(ecosystem)
Fixed versions
2.1.0
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2024-29800
timber/timber vulnerable to Deserialization of Untrusted Data
Summary
Timber is vulnerable to PHAR deserialization due to a lack of checking the input before passing it into the file_exists() function. If an attacker can upload files of any type to the server, he can pass in the phar:// protocol to unserialize the uploaded file and instantiate arbitrary PHP objects. This can lead to remote code execution especially when Timber is used with frameworks with documented POP chains like Wordpress/ vulnerable developer code.
Details
The vulnerability lies in the run function within the toJpg.php file. The two parameters passed into it are not checked or sanitized, hence an attacker could potentially inject malicious input leading to Deserialization of Untrusted Data, allowing for remote code execution:
image
PoC
Setup the following code in /var/www/html: vuln.php represents our use of Timber functions and phar-poc.php represents code with a vulnerable POP chain.
image
image
As an attacker, we generate our PHAR payload using the following exploit script:
image
Generate with:
image
then change extension file from .phar to valid extension as svg,jpg,...
image
and execute vuln.php with php vuln.php, you should see whoami being executed:
image
image
Impact
This vulnerability is capable of remote code execution if Timber is used with frameworks or developer code with vulnerable POP chains.
Recommended Fix
Filter the phar:// protocol.
High Basis: The source's own band: HIGH
2.0.0, fixed 2.1.0 (ecosystem)2.1.0
The export has no generic command for this ecosystem.
1.24.0, fixed 1.24.1 (ecosystem)1.24.1
The export has no generic command for this ecosystem.
0.16.6, fixed 1.23.1 (ecosystem)1.23.1
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0