WordPress security changelog
HIGH CVE-2005-3330 Modified

Snoopy: A security weakness

Snoopy 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 7.5 CVSS · cve@mitre.org
NVD score 7.5 CVSS 2.0 · nvd@nist.gov
Component
Snoopy
Plugin slug
snoopy
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Oct 27, 2005
Weakness
CWE-20 — Improper Input Validation

This CVE was published Oct 27, 2005 and is one of 1 known issue for this plugin.

Update, patch or deactivate.

Update Snoopy 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.

Technical description

The _httpsrequest function in Snoopy 1.2, as used in products such as (1) MagpieRSS, (2) WordPress, (3) Ampache, and (4) Jinzora, allows remote attackers to execute arbitrary commands via shell metacharacters in an HTTPS URL to an SSL protected web page, which is not properly handled by the fetch function.

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

Primary and upstream sources