WordPress up to 4.8.2 Password Hash pluggable.php MD5 inadequate encryption
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
5.3 | $0-$5k | 0.00 |
A vulnerability was found in WordPress up to 4.8.2 (Content Management System) and classified as problematic. This issue affects some unknown functionality of the file wp-includes/pluggable.php of the component Password Hash. The manipulation with an unknown input leads to a inadequate encryption vulnerability (MD5). Using CWE to declare the problem leads to CWE-326. The product stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required. Impacted is confidentiality. The summary by CVE is:
WordPress through 4.8.2 uses a weak MD5-based password hashing algorithm, which makes it easier for attackers to determine cleartext values by leveraging access to the hash values. NOTE: the approach to changing this may not be fully compatible with certain use cases, such as migration of a WordPress site from a web host that uses a recent PHP version to a different web host that uses PHP 5.2. These use cases are plausible (but very unlikely) based on statistics showing widespread deployment of WordPress with obsolete PHP versions.
The bug was discovered 06/20/2012. The weakness was disclosed 10/19/2017 (Website). The advisory is shared at core.trac.wordpress.org. The identification of this vulnerability is CVE-2012-6707 since 10/19/2017. An attack has to be approached locally. A simple authentication is required for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1600 for this issue. The following code is the reason for this vulnerability:
$wp_hasher = new PasswordHash(8, true);
The vulnerability was handled as a non-public zero-day exploit for at least 1947 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:wp-includes/pluggable.php it is possible to find vulnerable targets with Google Hacking. The vulnerability scanner Nessus provides a plugin with the ID 104356 (WordPress < 4.8.3 Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family CGI abuses and running in the context r.
Upgrading eliminates this vulnerability. A possible mitigation has been published 2 weeks after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (104356). The entry VDB-107809 is pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CVSSv2
AV | AC | Au | C | I | A |
---|---|---|---|---|---|
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
---|---|---|---|---|---|
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Name: MD5Class: Inadequate encryption / MD5
CWE: CWE-326 / CWE-310
CAPEC: 🔍
ATT&CK: 🔍
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
0-Day | unlock | unlock | unlock | unlock |
---|---|---|---|---|
Today | unlock | unlock | unlock | unlock |
Nessus ID: 104356
Nessus Name: WordPress < 4.8.3 Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
OpenVAS ID: 861726
OpenVAS Name: WordPress through 4.8.2 Weak Password Hash Algorithm
OpenVAS File: 🔍
OpenVAS Family: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
06/20/2012 🔍10/19/2017 🔍
10/19/2017 🔍
10/19/2017 🔍
10/20/2017 🔍
10/31/2017 🔍
11/02/2017 🔍
01/04/2023 🔍
Sources
Product: wordpress.comAdvisory: 21022
Status: Not defined
CVE: CVE-2012-6707 (🔍)
GCVE (CVE): GCVE-0-2012-6707
GCVE (VulDB): GCVE-100-108257
SecurityFocus: 101638
See also: 🔍
Entry
Created: 10/20/2017 08:46 AMUpdated: 01/04/2023 09:17 AM
Changes: 10/20/2017 08:46 AM (70), 06/07/2020 06:59 PM (7), 01/04/2023 09:17 AM (5)
Complete: 🔍
Cache ID: 18:207:40
No comments yet. Languages: en.
Please log in to comment.