CVE-2008-4106
What it is
WordPress before 2.6.2 does not properly handle MySQL warnings about insertion of username strings that exceed the maximum column width of the user_login column, and does not properly handle space characters when comparing usernames, which allows remote attackers to change an arbitrary user's password to a random value by registering a similar username and then requesting a password reset, related to a "SQL column truncation vulnerability." NOTE: the attacker can discover the random password by also exploiting CVE-2008-4107.
At a glance
- Exploitability
- Can be exploited over the network without logging in. Limited direct impact.
- Exploit odds
- 5.5% 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.5% in the next 30 days (EPSS).
- Severity: 5.1 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 5.5% · EPSS, next 30 days
- Weakness
- CWE-20 · Improper input validation
- Record status
- Modified
Affected
- WordPress ≤ 2.6.1
- WordPress 0.71-gold
- WordPress 1.0-platinum
- WordPress 1.0.1-miles
- WordPress 1.0.2-blakey
- WordPress 1.2-delta
- WordPress 1.2-mingus
- WordPress 1.2.1
Attack profile CVSS 2.0 · 5.1
- Attack vector
- Network
- Complexity
- High
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
Raw vector
AV:N/AC:H/Au:N/C:P/I:P/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-2008-4106.md and follow it. Check whether this project is affected by CVE-2008-4106. 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://secunia.com/advisories/31870
- http://wordpress.org/development/2008/09/wordpress-262/
- http://secunia.com/advisories/31870
- http://wordpress.org/development/2008/09/wordpress-262/
References
- http://marc.info/?l=oss-security&m=122152830017099&w=2
- http://secunia.com/advisories/31737
- http://secunia.com/advisories/31870
- http://securityreason.com/securityalert/4272
- http://securitytracker.com/id?1020869
- http://wordpress.org/development/2008/09/wordpress-262/
- http://www.debian.org/security/2009/dsa-1871
- http://www.openwall.com/lists/oss-security/2008/09/11/6
- http://www.securityfocus.com/archive/1/496287/100/0/threaded
- http://www.securityfocus.com/bid/31068
- http://www.sektioneins.de/advisories/SE-2008-05.txt
- http://www.suspekt.org/2008/08/18/mysql-and-sql-column-truncation-vulnerabilities/
- http://www.vupen.com/english/advisories/2008/2553
- https://www.exploit-db.com/exploits/6397
- https://www.exploit-db.com/exploits/6421
- https://www.redhat.com/archives/fedora-package-announce/2008-September/msg00607.html
- https://www.redhat.com/archives/fedora-package-announce/2008-September/msg00629.html
- http://marc.info/?l=oss-security&m=122152830017099&w=2
- http://secunia.com/advisories/31737
- http://secunia.com/advisories/31870
- http://securityreason.com/securityalert/4272
- http://securitytracker.com/id?1020869
- http://wordpress.org/development/2008/09/wordpress-262/
- http://www.debian.org/security/2009/dsa-1871
- http://www.openwall.com/lists/oss-security/2008/09/11/6