GIVE YOUR AGENT THE EVIDENCE

Set up in your agent.

One prompt to get started. Paste it into your coding agent to connect cve.new through MCP and bring vulnerability context into your workflow.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

GIVE YOUR AGENT THE EVIDENCE

Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

cve.new
GHSA-6363-v5m4-fvq3high8.0

timber/timber vulnerable to Deserialization of Untrusted Data

Check your stack

The advisory, in context

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.

Affected packages

Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.

Ecosystem versions

From 2.0.0 before 2.1.0

Fixed in 2.1.0

1 explicitly affected versions

2.0.0

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "2.0.0"
        },
        {
          "fixed": "2.1.0"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "2.0.0"
  ]
}
Ecosystem versions

From 1.24.0 before 1.24.1

Fixed in 1.24.1

1 explicitly affected versions

1.24.0

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "1.24.0"
        },
        {
          "fixed": "1.24.1"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "1.24.0"
  ]
}
Ecosystem versions

From 0.16.6 before 1.23.1

Fixed in 1.23.1

115 explicitly affected versions

0.16.6, 0.16.8, 0.17.0, 0.17.2, 0.18.0, 0.18.1, 0.19.0, 0.19.1, 0.19.2, 0.20.0, 0.20.1, 0.20.10, 0.20.2, 0.20.3, 0.20.4, 0.20.5, 0.20.6, 0.20.7, 0.20.8, 0.20.9, 0.21.0, 0.21.10, 0.21.2, 0.21.3, 0.21.4, 0.21.5, 0.21.6, 0.21.7, 0.21.8, 0.21.9, 0.22.0, 0.22.1, 0.22.2, 0.22.3, 0.22.4, 0.22.5, 0.22.6, 1.0-rc2, 1.0.0, 1.0.0-rc3, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.1.0, 1.1.1, 1.1.10, 1.1.11, 1.1.12, 1.1.2, 1.1.3, 1.1.4, 1.1.5, 1.1.6, 1.1.7, 1.1.7.1, 1.1.8, 1.1.9, 1.10.0, 1.10.1, 1.11.0, 1.12.0, 1.12.1, 1.13.0, 1.14.0, 1.15.0, 1.15.1, 1.15.2, 1.16.0, 1.17.0, 1.18.0, 1.18.1, 1.18.2, 1.19.0, 1.19.1, 1.19.2, 1.2.0, 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.20.0, 1.21.0, 1.22.0, 1.22.1, 1.23.0, 1.3.0, 1.3.0-beta, 1.3.0-rc1, 1.3.0-rc2, 1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.4.0, 1.4.1, 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.7.0, 1.7.1, 1.8.0, 1.8.1, 1.8.2, 1.8.3, 1.8.4, 1.9.0, 1.9.1, 1.9.2, 1.9.3, 1.9.4, 1.9.5, v1.0-rc.1

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "0.16.6"
        },
        {
          "fixed": "1.23.1"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "0.16.6",
    "0.16.8",
    "0.17.0",
    "0.17.2",
    "0.18.0",
    "0.18.1",
    "0.19.0",
    "0.19.1",
    "0.19.2",
    "0.20.0",
    "0.20.1",
    "0.20.10",
    "0.20.2",
    "0.20.3",
    "0.20.4",
    "0.20.5",
    "0.20.6",
    "0.20.7",
    "0.20.8",
    "0.20.9",
    "0.21.0",
    "0.21.10",
    "0.21.2",
    "0.21.3",
    "0.21.4",
    "0.21.5",
    "0.21.6",
    "0.21.7",
    "0.21.8",
    "0.21.9",
    "0.22.0",
    "0.22.1",
    "0.22.2",
    "0.22.3",
    "0.22.4",
    "0.22.5",
    "0.22.6",
    "1.0-rc2",
    "1.0.0",
    "1.0.0-rc3",
    "1.0.1",
    "1.0.2",
    "1.0.3",
    "1.0.4",
    "1.0.5",
    "1.1.0",
    "1.1.1",
    "1.1.10",
    "1.1.11",
    "1.1.12",
    "1.1.2",
    "1.1.3",
    "1.1.4",
    "1.1.5",
    "1.1.6",
    "1.1.7",
    "1.1.7.1",
    "1.1.8",
    "1.1.9",
    "1.10.0",
    "1.10.1",
    "1.11.0",
    "1.12.0",
    "1.12.1",
    "1.13.0",
    "1.14.0",
    "1.15.0",
    "1.15.1",
    "1.15.2",
    "1.16.0",
    "1.17.0",
    "1.18.0",
    "1.18.1",
    "1.18.2",
    "1.19.0",
    "1.19.1",
    "1.19.2",
    "1.2.0",
    "1.2.1",
    "1.2.2",
    "1.2.3",
    "1.2.4",
    "1.20.0",
    "1.21.0",
    "1.22.0",
    "1.22.1",
    "1.23.0",
    "1.3.0",
    "1.3.0-beta",
    "1.3.0-rc1",
    "1.3.0-rc2",
    "1.3.1",
    "1.3.2",
    "1.3.3",
    "1.3.4",
    "1.4.0",
    "1.4.1",
    "1.5.0",
    "1.5.1",
    "1.5.2",
    "1.6.0",
    "1.7.0",
    "1.7.1",
    "1.8.0",
    "1.8.1",
    "1.8.2",
    "1.8.3",
    "1.8.4",
    "1.9.0",
    "1.9.1",
    "1.9.2",
    "1.9.3",
    "1.9.4",
    "1.9.5",
    "v1.0-rc.1"
  ]
}

References