For mod_access_referer issue:

- Correct spelling.
- `null' in `null pointer' should not be all caps
- Correct the secunia.com URL (it did not identify this particular bug)

1 files changed, 5 insertions, 4 deletions

diff --git a/security/vuxml/vuln.xml b/security/vuxml/vuln.xml
index a6e375348074..e82ad87488c7 100644
--- a/security/vuxml/vuln.xml
+++ b/security/vuxml/vuln.xml
@@ -1626,7 +1626,7 @@ http_access deny Gopher</pre>
   </vuln>
 
   <vuln vid="af747389-42ba-11d9-bd37-00065be4b5b6">
-    <topic>mod_access_referer -- NULL pointer dereference vulnerability</topic>
+    <topic>mod_access_referer -- null pointer dereference vulnerability</topic>
     <affects>
       <package>
 	<name>mod_access_referer</name>
@@ -1638,21 +1638,22 @@ http_access deny Gopher</pre>
 	<p>A malformed <q>Referer</q> header field causes the Apache
 	  ap_parse_uri_components function to discard it with the
 	  result that a pointer is not initialized.  The
-	  mod_acesses_referer module does not take this into account
+	  mod_access_referer module does not take this into account
 	  with the result that it may use such a pointer.</p>
-	<p>The NULL pointer vulnerability may possibly be used in a
+	<p>The null pointer vulnerability may possibly be used in a
 	  remote denial of service attack against affected Apache
 	  servers.</p>
       </body>
     </description>
     <references>
       <bid>7375</bid>
-      <url>http://secunia.com/product/1477/</url>
+      <url>http://secunia.com/advisories/8612/</url>
       <mlist>http://marc.theaimsgroup.com/?l=full-disclosure&amp;m=105053485515811</mlist>
     </references>
     <dates>
       <discovery>2003-04-16</discovery>
       <entry>2004-12-11</entry>
+      <modified>2005-01-13</modified>
     </dates>
   </vuln>