WordPress 3.5.2 Media Library multi_resize Installation Path information disclosure ⚔ [Disputed]

Summaryinfo

A vulnerability was found in WordPress 3.5.2. It has been rated as problematic. The affected element is the function get_allowed_mime_types/set_url_scheme/comment_form/parent_dropdown/wp_new_comment/mb_internal_encoding/get_post_type_archive_feed_link/WP_Image_Editor::multi_resize of the component Media Library. This manipulation causes information disclosure (Installation Path). No exploit exists. It is still unclear if this vulnerability genuinely exists. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in WordPress 3.5.2 (Content Management System). It has been declared as problematic. Affected by this vulnerability is the function get_allowed_mime_types/set_url_scheme/comment_form/parent_dropdown/wp_new_comment/mb_internal_encoding/get_post_type_archive_feed_link/WP_Image_Editor::multi_resize of the component Media Library. The manipulation with an unknown input leads to a information disclosure vulnerability (Installation Path). The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality.

The weakness was disclosed 09/27/2013 by MustLive as FPD ??????????? ? WordPress as confirmed advisory (Website). It is possible to read the advisory at websecurity.com.ua. The public release has been coordinated in cooperation with the project team. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.

The real existence of this vulnerability is still doubted at the moment.

Upgrading to version 3.6.1 eliminates this vulnerability. It is possible to mitigate the problem by applying the configuration setting display_errors = off. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at OSVDB (100484†). The entry VDB-11346 is pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• Content Management System

Name

• WordPress

Version

• 3.5.2

License

• open-source

Website

• Product: https://wordpress.com/

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion