You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by bu...@apache.org on 2013/03/24 12:30:02 UTC

svn commit: r855773 - in /websites/staging/httpd/trunk/content: ./ security/vulnerabilities-httpd.xml security/vulnerabilities_13.html

Author: buildbot
Date: Sun Mar 24 11:30:02 2013
New Revision: 855773

Log:
Staging update by buildbot for httpd

Modified:
    websites/staging/httpd/trunk/content/   (props changed)
    websites/staging/httpd/trunk/content/security/vulnerabilities-httpd.xml
    websites/staging/httpd/trunk/content/security/vulnerabilities_13.html

Propchange: websites/staging/httpd/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun Mar 24 11:30:02 2013
@@ -1 +1 @@
-1451675
+1460315

Modified: websites/staging/httpd/trunk/content/security/vulnerabilities-httpd.xml
==============================================================================
--- websites/staging/httpd/trunk/content/security/vulnerabilities-httpd.xml (original)
+++ websites/staging/httpd/trunk/content/security/vulnerabilities-httpd.xml Sun Mar 24 11:30:02 2013
@@ -1759,7 +1759,7 @@ vulnerable to cross-site request forgery
 <affects prod="httpd" version="2.2.0"/>
 </issue>
 
-<issue fixed="1.3.42" public="2010127" reported="20091230" released="20100203">
+<issue fixed="1.3.42" public="20100127" reported="20091230" released="20100203">
 <cve name="CVE-2010-0010"/>
 <severity level="3">moderate</severity>      
 <title>mod_proxy overflow on 64-bit systems</title>

Modified: websites/staging/httpd/trunk/content/security/vulnerabilities_13.html
==============================================================================
--- websites/staging/httpd/trunk/content/security/vulnerabilities_13.html (original)
+++ websites/staging/httpd/trunk/content/security/vulnerabilities_13.html Sun Mar 24 11:30:02 2013
@@ -131,7 +131,7 @@ via a carefully crafted response.
   </dd>
   <dd>
   Reported to security team: 30th December 2009<br/>
-  Issue public: 7th December 2010<br/></dd>
+  Issue public: 27th January 2010<br/></dd>
   <dd>
   Update Released: 3rd February 2010<br/></dd>
   <dd>