What is CVE-2024-29800?

CVE-2024-29800 is a high-severity insecure deserialization vulnerability in timber/timber (composer), affecting versions = 2.0.0. It is fixed in 2.1.0, 1.24.1, 1.23.1. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.

How severe is CVE-2024-29800?

CVE-2024-29800 has a CVSS score of 8.0 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of timber/timber are affected by CVE-2024-29800?

timber/timber (composer) versions = 2.0.0 is affected.

Is there a fix for CVE-2024-29800?

Yes. CVE-2024-29800 is fixed in 2.1.0, 1.24.1, 1.23.1. Upgrade to this version or later.

Is CVE-2024-29800 exploitable, and should I be worried?

Whether CVE-2024-29800 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2024-29800 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2024-29800?

Upgrade: timber/timber to 2.1.0 or later, timber/timber to 1.24.1 or later, timber/timber to 1.23.1 or later.

CVE-2024-29800 in timber/timber

Summary

timber/timber vulnerable to Deserialization of Untrusted Data

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:

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.

As an attacker, we generate our PHAR payload using the following exploit script:

Generate with:

then change extension file from .phar to valid extension as svg,jpg,...

and execute vuln.php with php vuln.php, you should see whoami being executed:

Impact

This vulnerability is capable of remote code execution if Timber is used with frameworks or developer code with vulnerable POP chains.

Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect. Typical impact: arbitrary code execution or logic abuse.

CVE-2024-29800 has a CVSS score of 8.0 (High). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.1.0, 1.24.1, 1.23.1); upgrading removes the vulnerable code path.

Affected versions

timber/timber (= 2.0.0) timber/timber (= 1.24.0) timber/timber (>= 0.16.6, < 1.23.1)

Security releases

timber/timber → 2.1.0 (composer) timber/timber → 1.24.1 (composer) timber/timber → 1.23.1 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Filter the phar:// protocol.

Frequently Asked Questions

What is CVE-2024-29800? CVE-2024-29800 is a high-severity insecure deserialization vulnerability in timber/timber (composer), affecting versions = 2.0.0. It is fixed in 2.1.0, 1.24.1, 1.23.1. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.
How severe is CVE-2024-29800? CVE-2024-29800 has a CVSS score of 8.0 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of timber/timber are affected by CVE-2024-29800? timber/timber (composer) versions = 2.0.0 is affected.
Is there a fix for CVE-2024-29800? Yes. CVE-2024-29800 is fixed in 2.1.0, 1.24.1, 1.23.1. Upgrade to this version or later.
Is CVE-2024-29800 exploitable, and should I be worried? Whether CVE-2024-29800 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2024-29800 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2024-29800?
- Upgrade timber/timber to 2.1.0 or later
- Upgrade timber/timber to 1.24.1 or later
- Upgrade timber/timber to 1.23.1 or later