WordPress security changelog
MEDIUM CVE-2011-4106 Modified

Timthumb: A security weakness

Timthumb is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.

CVE / CNA score 6.8 CVSS · secalert@redhat.com
NVD score 6.8 CVSS 2.0 · nvd@nist.gov
Component
Timthumb
Plugin slug
timthumb
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Oct 26, 2013
Weakness
CWE-20 — Improper Input Validation

This CVE was published Oct 26, 2013 and is one of 2 known issues for this plugin.

What to do

Update, patch or deactivate.

Update Timthumb to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

TimThumb (timthumb.php) before 2.0 does not validate the entire source with the domain white list, which allows remote attackers to upload and execute arbitrary code via a URL containing a white-listed domain in the src parameter, then accessing it via a direct request to the file in the cache directory, as exploited in the wild in August 2011.

NVD vector: AV:N/AC:M/Au:N/C:P/I:P/A:P

References

Primary and upstream sources