CVE-2009-3622
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network without logging in. Limited direct impact.
- Exploit odds
- 5.8% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 5.8% in the next 30 days (EPSS).
- Severity: 4.3 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 5.8% · EPSS, next 30 days
- Weakness
- CWE-310
- Record status
- Modified
Affected
- WordPress ≤ 2.8.4
Attack profile CVSS 2.0 · 4.3
- Attack vector
- Network
- Complexity
- Medium
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
Raw vector
AV:N/AC:M/Au:N/C:N/I:N/A:P
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2009-3622.md and follow it. Check whether this project is affected by CVE-2009-3622. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- http://rooibo.wordpress.com/2009/10/17/agujero-de-seguridad-en-wordpress/
- http://wordpress.org/development/2009/10/wordpress-2-8-5-hardening-release/
- http://www.vupen.com/english/advisories/2009/2986
- http://rooibo.wordpress.com/2009/10/17/agujero-de-seguridad-en-wordpress/
- http://wordpress.org/development/2009/10/wordpress-2-8-5-hardening-release/
- http://www.vupen.com/english/advisories/2009/2986
References
- http://codes.zerial.org/php/wp-trackbacks_dos.phps
- http://marc.info/?l=oss-security&m=125612393329041&w=2
- http://marc.info/?l=oss-security&m=125614592004825&w=2
- http://rooibo.wordpress.com/2009/10/17/agujero-de-seguridad-en-wordpress/
- http://seclists.org/fulldisclosure/2009/Oct/263
- http://secunia.com/advisories/37088
- http://security-sh3ll.blogspot.com/2009/10/wordpress-resource-exhaustion-denial-of.html
- http://securitytracker.com/id?1023072
- http://wordpress.org/development/2009/10/wordpress-2-8-5-hardening-release/
- http://www.osvdb.org/59077
- http://www.vupen.com/english/advisories/2009/2986
- https://bugzilla.redhat.com/show_bug.cgi?id=530056
- https://exchange.xforce.ibmcloud.com/vulnerabilities/53884
- http://codes.zerial.org/php/wp-trackbacks_dos.phps
- http://marc.info/?l=oss-security&m=125612393329041&w=2
- http://marc.info/?l=oss-security&m=125614592004825&w=2
- http://rooibo.wordpress.com/2009/10/17/agujero-de-seguridad-en-wordpress/
- http://seclists.org/fulldisclosure/2009/Oct/263
- http://secunia.com/advisories/37088
- http://security-sh3ll.blogspot.com/2009/10/wordpress-resource-exhaustion-denial-of.html
- http://securitytracker.com/id?1023072
- http://wordpress.org/development/2009/10/wordpress-2-8-5-hardening-release/
- http://www.osvdb.org/59077
- http://www.vupen.com/english/advisories/2009/2986
- https://bugzilla.redhat.com/show_bug.cgi?id=530056