CVE-2014-9037: Medium severity mageia vulnerability
Published Nov 25, 2014
·Updated
WordPress before 3.7.5, 3.8.x before 3.8.5, 3.9.x before 3.9.3, and 4.x before 4.0.1 might allow remote attackers to obtain access to an account idle since 2008 by leveraging an improper PHP dynamic type comparison for an MD5 hash.
Affected Software
14 affected components
Mageia Project Mageia=3
Mageia Project Mageia=4
WordPress WordPress<=3.7.4
WordPress WordPress=3.8
WordPress WordPress=3.8.1
WordPress WordPress=3.8.2
WordPress WordPress=3.8.3
WordPress WordPress=3.8.4
WordPress WordPress=3.9
WordPress WordPress=3.9.1
WordPress WordPress=3.9.2
WordPress WordPress=4.0
Debian Debian Linux=7.0
Debian Debian Linux=8.0
Remediation
Patch Available
Event History
Nov 25, 2014
CVE Published
via MITRE·11:00 PM
Data Sourced
via MITRE·11:00 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2014-9037?
CVE-2014-9037 is classified as a moderate severity vulnerability due to its potential for unauthorized account access.
2
How do I fix CVE-2014-9037?
Fixing CVE-2014-9037 involves upgrading to WordPress versions 3.7.5, 3.8.5, 3.9.3, or 4.0.1 or later.
3
Which versions of WordPress are affected by CVE-2014-9037?
CVE-2014-9037 affects WordPress versions below 3.7.5, 3.8.x before 3.8.5, 3.9.x before 3.9.3, and 4.x before 4.0.1.
4
What can attackers do with CVE-2014-9037?
Attackers exploiting CVE-2014-9037 may gain access to accounts that have been idle since 2008.
5
Is Mageia 3 or 4 affected by CVE-2014-9037?
Yes, Mageia versions 3 and 4 are affected by CVE-2014-9037.