CVE-2009-3622
published 2009-10-23CVE-2009-3622: Algorithmic complexity vulnerability in wp-trackback.php in WordPress before 2.8.5 allows remote attackers to cause a denial of service (CPU consumption and…
PriorityP424medium4.3CVSS 2.0
AVNACMAuNCNINAP
EPSS
5.83%
92.3th percentile
Algorithmic complexity vulnerability in wp-trackback.php in WordPress before 2.8.5 allows remote attackers to cause a denial of service (CPU consumption and server hang) via a long title parameter in conjunction with a charset parameter composed of many comma-separated "UTF-8" substrings, related to the mb_convert_encoding function in PHP.
Affected
6 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | wordpress | < wordpress 2.8.5-1 (bookworm) | wordpress 2.8.5-1 (bookworm) |
| wordpress | wordpress | <= 2.8.4 | — |
| wordpress | wordpress | >= 0 < 2.8.5-1 | 2.8.5-1 |
| wordpress | wordpress | >= 0 < 2.8.5-1 | 2.8.5-1 |
| wordpress | wordpress | >= 0 < 2.8.5-1 | 2.8.5-1 |
| wordpress | wordpress | >= 0 < 2.8.5-1 | 2.8.5-1 |
CVSS provenance
nvdv2.04.3MEDIUMAV:N/AC:M/Au:N/C:N/I:N/A:P
osv4.3MEDIUM
vendor_debian4.3MEDIUM
vendor_redhat4.3MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-m4j7-w5vj-fwff: Algorithmic complexity vulnerability in wp-trackback
ghsa_unreviewed·2022-05-02
CVE-2009-3622 [MEDIUM] GHSA-m4j7-w5vj-fwff: Algorithmic complexity vulnerability in wp-trackback
Algorithmic complexity vulnerability in wp-trackback.php in WordPress before 2.8.5 allows remote attackers to cause a denial of service (CPU consumption and server hang) via a long title parameter in conjunction with a charset parameter composed of many comma-separated "UTF-8" substrings, related to the mb_convert_encoding function in PHP.
OSV
CVE-2009-3622: Algorithmic complexity vulnerability in wp-trackback
osv·2009-10-23·CVSS 4.3
CVE-2009-3622 [MEDIUM] CVE-2009-3622: Algorithmic complexity vulnerability in wp-trackback
Algorithmic complexity vulnerability in wp-trackback.php in WordPress before 2.8.5 allows remote attackers to cause a denial of service (CPU consumption and server hang) via a long title parameter in conjunction with a charset parameter composed of many comma-separated "UTF-8" substrings, related to the mb_convert_encoding function in PHP.
Red Hat
WordPress: Resource exhaustion (DoS)
vendor_redhat·2009-10-20·CVSS 4.3
CVE-2009-3622 [MEDIUM] WordPress: Resource exhaustion (DoS)
WordPress: Resource exhaustion (DoS)
Algorithmic complexity vulnerability in wp-trackback.php in WordPress before 2.8.5 allows remote attackers to cause a denial of service (CPU consumption and server hang) via a long title parameter in conjunction with a charset parameter composed of many comma-separated "UTF-8" substrings, related to the mb_convert_encoding function in PHP.
Debian
CVE-2009-3622: wordpress - Algorithmic complexity vulnerability in wp-trackback.php in WordPress before 2.8...
vendor_debian·2009·CVSS 4.3
CVE-2009-3622 [MEDIUM] CVE-2009-3622: wordpress - Algorithmic complexity vulnerability in wp-trackback.php in WordPress before 2.8...
Algorithmic complexity vulnerability in wp-trackback.php in WordPress before 2.8.5 allows remote attackers to cause a denial of service (CPU consumption and server hang) via a long title parameter in conjunction with a charset parameter composed of many comma-separated "UTF-8" substrings, related to the mb_convert_encoding function in PHP.
Scope: local
bookworm: resolved (fixed in 2.8.5-1)
bullseye: resolved (fixed in 2.8.5-1)
forky: resolved (fixed in 2.8.5-1)
sid: resolved (fixed in 2.8.5-1)
trixie: resolved (fixed in 2.8.5-1)
No detection rules found.
No public exploits indexed.
http://codes.zerial.org/php/wp-trackbacks_dos.phpshttp://marc.info/?l=oss-security&m=125612393329041&w=2http://marc.info/?l=oss-security&m=125614592004825&w=2http://rooibo.wordpress.com/2009/10/17/agujero-de-seguridad-en-wordpress/http://seclists.org/fulldisclosure/2009/Oct/263http://secunia.com/advisories/37088http://security-sh3ll.blogspot.com/2009/10/wordpress-resource-exhaustion-denial-of.htmlhttp://securitytracker.com/id?1023072http://wordpress.org/development/2009/10/wordpress-2-8-5-hardening-release/http://www.osvdb.org/59077http://www.vupen.com/english/advisories/2009/2986https://bugzilla.redhat.com/show_bug.cgi?id=530056https://exchange.xforce.ibmcloud.com/vulnerabilities/53884http://codes.zerial.org/php/wp-trackbacks_dos.phpshttp://marc.info/?l=oss-security&m=125612393329041&w=2http://marc.info/?l=oss-security&m=125614592004825&w=2http://rooibo.wordpress.com/2009/10/17/agujero-de-seguridad-en-wordpress/http://seclists.org/fulldisclosure/2009/Oct/263http://secunia.com/advisories/37088http://security-sh3ll.blogspot.com/2009/10/wordpress-resource-exhaustion-denial-of.htmlhttp://securitytracker.com/id?1023072http://wordpress.org/development/2009/10/wordpress-2-8-5-hardening-release/http://www.osvdb.org/59077http://www.vupen.com/english/advisories/2009/2986https://bugzilla.redhat.com/show_bug.cgi?id=530056https://exchange.xforce.ibmcloud.com/vulnerabilities/53884
2009-10-23
Published