| Summary: | <www-apps/wordpress-3.5.2 : multiple vulnerabilities (CVE-2013-{2199,2200,2201,2202,2203,2204,2205}) | ||
|---|---|---|---|
| Product: | Gentoo Security | Reporter: | Agostino Sarubbo <ago> |
| Component: | Vulnerabilities | Assignee: | Gentoo Security <security> |
| Status: | RESOLVED FIXED | ||
| Severity: | trivial | CC: | tampakrap, web-apps |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://bugzilla.redhat.com/show_bug.cgi?id=976784 | ||
| Whiteboard: | ~4 [noglsa] | ||
| Package list: | Runtime testing required: | --- | |
22 Jun 2013; Tim Harder <radhermit@gentoo.org> +wordpress-3.5.2.ebuild: Version bump, expand CMS acronym in DESCRIPTION (bug #474030). Closing as noglsa CVE-2013-2205 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-2205): The default configuration of SWFUpload in WordPress before 3.5.2 has an unrestrictive security.allowDomain setting, which allows remote attackers to bypass the Same Origin Policy and conduct cross-site scripting (XSS) attacks via a crafted web site. CVE-2013-2204 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-2204): moxieplayer.as in Moxiecode moxieplayer, as used in the TinyMCE Media plugin in WordPress before 3.5.2 and other products, does not consider the presence of a # (pound sign) character during extraction of the QUERY_STRING, which allows remote attackers to pass arbitrary parameters to a Flash application, and conduct content-spoofing attacks, via a crafted string after a ? (question mark) character. CVE-2013-2203 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-2203): WordPress before 3.5.2, when the uploads directory forbids write access, allows remote attackers to obtain sensitive information via an invalid upload request, which reveals the absolute path in an XMLHttpRequest error message. CVE-2013-2202 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-2202): WordPress before 3.5.2 allows remote attackers to read arbitrary files via an oEmbed XML provider response containing an external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) issue. CVE-2013-2201 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-2201): Multiple cross-site scripting (XSS) vulnerabilities in WordPress before 3.5.2 allow remote attackers to inject arbitrary web script or HTML via vectors involving (1) uploads of media files, (2) editing of media files, (3) installation of plugins, (4) updates to plugins, (5) installation of themes, or (6) updates to themes. CVE-2013-2200 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-2200): WordPress before 3.5.2 does not properly check the capabilities of roles, which allows remote authenticated users to bypass intended restrictions on publishing and authorship reassignment via unspecified vectors. CVE-2013-2199 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-2199): The HTTP API in WordPress before 3.5.2 allows remote attackers to send HTTP requests to intranet servers via unspecified vectors, related to a Server-Side Request Forgery (SSRF) issue, a similar vulnerability to CVE-2013-0235. |
From ${URL} : On Friday, 2013-06-21 WordPress upstream is about to release new WordPress v3.5.2 version, correcting the following security flaws: * CVE-2013-2199 - SSRF, multiple vulnerabilities: Inadequate SSRF protection for HTTP requests where the user can provide a URL can allow for attacks against the intranet and other sites. This is a continuation of work related to CVE-2013-0235, which was specific to SSRF in pingback requests and was fixed in 3.5.1. * CVE-2013-2200 - Privilege escalation allowing contributors to publish posts: Inadequate checking of a user's capabilities could allow them to publish posts when their user role should not allow for it; and to assign posts to other authors. * CVE-2013-2201 - XSS, multiple vulnerabilities: Inadequate escaping allowed an administrator to trigger a cross-site scripting vulnerability through the uploading of media files and plugins. * CVE-2013-2202 - XXE via oEmbed: The processing of an oEmbed response is vulnerable to an XXE. * CVE-2013-2203 - Full Path Disclosure during File Upload: If the uploads directory is not writable, error message data returned via XHR will include a full path to the directory. And two security flaws in external products: * CVE-2013-2204 - Content Spoofing in the MoxieCode (TinyMCE) MoxiePlayer project: Upstream patch: https://github.com/moxiecode/moxieplayer/commit/b61ac518ffa2657e2dc9019b2 * CVE-2013-2205 - Cross-domain XSS in SWFUpload (again): Fix: Removing security.allowDomain("*") and only allow access from the same domain. External References: http://codex.wordpress.org/Version_3.5.2 @maintainer(s): after the bump, in case we need to stabilize the package, please say explicitly if it is ready for the stabilization or not.