summaryrefslogtreecommitdiff
path: root/metadata/glsa/glsa-200410-12.xml
diff options
context:
space:
mode:
authorV3n3RiX <venerix@redcorelinux.org>2017-10-09 18:53:29 +0100
committerV3n3RiX <venerix@redcorelinux.org>2017-10-09 18:53:29 +0100
commit4f2d7949f03e1c198bc888f2d05f421d35c57e21 (patch)
treeba5f07bf3f9d22d82e54a462313f5d244036c768 /metadata/glsa/glsa-200410-12.xml
reinit the tree, so we can have metadata
Diffstat (limited to 'metadata/glsa/glsa-200410-12.xml')
-rw-r--r--metadata/glsa/glsa-200410-12.xml67
1 files changed, 67 insertions, 0 deletions
diff --git a/metadata/glsa/glsa-200410-12.xml b/metadata/glsa/glsa-200410-12.xml
new file mode 100644
index 000000000000..c25cbd1897e6
--- /dev/null
+++ b/metadata/glsa/glsa-200410-12.xml
@@ -0,0 +1,67 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
+<glsa id="200410-12">
+ <title>WordPress: HTTP response splitting and XSS vulnerabilities</title>
+ <synopsis>
+ WordPress contains HTTP response splitting and cross-site scripting
+ vulnerabilities.
+ </synopsis>
+ <product type="ebuild">wordpress</product>
+ <announced>2004-10-14</announced>
+ <revised>2006-05-22: 04</revised>
+ <bug>65798</bug>
+ <access>remote</access>
+ <affected>
+ <package name="www-apps/wordpress" auto="yes" arch="*">
+ <unaffected range="ge">1.2.2</unaffected>
+ <vulnerable range="lt">1.2.2</vulnerable>
+ </package>
+ </affected>
+ <background>
+ <p>
+ WordPress is a PHP and MySQL based content management and publishing
+ system.
+ </p>
+ </background>
+ <description>
+ <p>
+ Due to the lack of input validation in the administration panel
+ scripts, WordPress is vulnerable to HTTP response splitting and
+ cross-site scripting attacks.
+ </p>
+ </description>
+ <impact type="low">
+ <p>
+ A malicious user could inject arbitrary response data, leading to
+ content spoofing, web cache poisoning and other cross-site scripting or
+ HTTP response splitting attacks. This could result in compromising the
+ victim's data or browser.
+ </p>
+ </impact>
+ <workaround>
+ <p>
+ There is no known workaround at this time.
+ </p>
+ </workaround>
+ <resolution>
+ <p>
+ All WordPress users should upgrade to the latest version:
+ </p>
+ <code>
+ # emerge --sync
+ # emerge --ask --oneshot --verbose "&gt;=www-apps/wordpress-1.2.2"</code>
+ </resolution>
+ <references>
+ <uri link="https://wordpress.org/development/2004/12/one-point-two-two/">WordPress 1.2.2 Release Notes</uri>
+ <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2004-1584">CVE-2004-1584</uri>
+ </references>
+ <metadata tag="requester" timestamp="2004-10-12T11:43:21Z">
+ koon
+ </metadata>
+ <metadata tag="bugReady" timestamp="2004-10-12T11:44:27Z">
+ koon
+ </metadata>
+ <metadata tag="submitter" timestamp="2004-10-12T21:40:26Z">
+ lewk
+ </metadata>
+</glsa>