Merge pull request #1751 from zapbot/update-site-content

Update site content

Author: thc202

alerttags/cwe-601/index.html

@@ -170,7 +170,7 @@ <h4><a href="https://cwe.mitre.org/data/definitions/601.html">https://cwe.mitre.
 
 
                <tr>
-                  <td><a href="/docs/alerts/10028/">Open Redirect</a></td>
+                  <td><a href="/docs/alerts/10028/">Off-site Redirect</a></td>
                   <td><a href=""></a></td>
                </tr>
 

alerttags/cwe-601/index.xml

@@ -36,11 +36,11 @@
       <description>&lt;p&gt;URL redirectors represent common functionality employed by web sites to forward an incoming request to an alternate resource. This can be done for a variety of reasons and is often done to allow resources to be moved within the directory structure and to avoid breaking functionality for users that request the resource at its previous location. URL redirectors may also be used to implement load balancing, leveraging abbreviated URLs or recording outgoing links. It is this last implementation which is often used in phishing attacks as described in the example below. URL redirectors do not necessarily represent a direct security vulnerability but can be abused by attackers trying to social engineer victims into believing that they are navigating to a site other than the true destination.&lt;/p&gt;</description>
     </item>
     <item>
-      <title>Open Redirect</title>
+      <title>Off-site Redirect</title>
       <link>/docs/alerts/10028/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       <guid>/docs/alerts/10028/</guid>
-      <description>&lt;p&gt;Open redirects are one of the OWASP 2010 Top Ten vulnerabilities. This check looks at user-supplied input in query string parameters and POST data to identify where open redirects might be possible. Open redirects occur when an application allows user-supplied input (e.g. &lt;a href=&#34;https://nottrusted.com&#34;&gt;https://nottrusted.com&lt;/a&gt;) to control an offsite redirect. This is generally a pretty accurate way to find where 301 or 302 redirects could be exploited by spammers or phishing attacks.&lt;/p&gt;</description>
+      <description>&lt;p&gt;Open redirects are one of the OWASP 2010 Top Ten vulnerabilities. This check looks at user-supplied input in query string parameters and POST data to identify where open redirects might be possible. Open redirects occur when an application allows user-supplied input (e.g. &lt;a href=&#34;https://nottrusted.com&#34;&gt;https://nottrusted.com&lt;/a&gt;) to control an off-site destination. This is generally a pretty accurate way to find where 301 or 302 redirects could be exploited by spammers or phishing attacks.&lt;/p&gt;</description>
     </item>
   </channel>
 </rss>

alerttags/owasp_2017_a01/index.html

@@ -242,7 +242,7 @@ <h4><a href="https://owasp.org/www-project-top-ten/2017/A1_2017-Injection.html">
 
 
                <tr>
-                  <td><a href="/docs/alerts/10028/">Open Redirect</a></td>
+                  <td><a href="/docs/alerts/10028/">Off-site Redirect</a></td>
                   <td><a href=""></a></td>
                </tr>
 

alerttags/owasp_2017_a01/index.xml

@@ -120,11 +120,11 @@
       <description>&lt;p&gt;MongoDB query injection may be possible.&lt;/p&gt;</description>
     </item>
     <item>
-      <title>Open Redirect</title>
+      <title>Off-site Redirect</title>
       <link>/docs/alerts/10028/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       <guid>/docs/alerts/10028/</guid>
-      <description>&lt;p&gt;Open redirects are one of the OWASP 2010 Top Ten vulnerabilities. This check looks at user-supplied input in query string parameters and POST data to identify where open redirects might be possible. Open redirects occur when an application allows user-supplied input (e.g. &lt;a href=&#34;https://nottrusted.com&#34;&gt;https://nottrusted.com&lt;/a&gt;) to control an offsite redirect. This is generally a pretty accurate way to find where 301 or 302 redirects could be exploited by spammers or phishing attacks.&lt;/p&gt;</description>
+      <description>&lt;p&gt;Open redirects are one of the OWASP 2010 Top Ten vulnerabilities. This check looks at user-supplied input in query string parameters and POST data to identify where open redirects might be possible. Open redirects occur when an application allows user-supplied input (e.g. &lt;a href=&#34;https://nottrusted.com&#34;&gt;https://nottrusted.com&lt;/a&gt;) to control an off-site destination. This is generally a pretty accurate way to find where 301 or 302 redirects could be exploited by spammers or phishing attacks.&lt;/p&gt;</description>
     </item>
     <item>
       <title>Parameter Tampering</title>

alerttags/owasp_2021_a03/index.html

@@ -272,7 +272,7 @@ <h4><a href="https://owasp.org/Top10/A03_2021-Injection/">https://owasp.org/Top1
 
 
                <tr>
-                  <td><a href="/docs/alerts/10028/">Open Redirect</a></td>
+                  <td><a href="/docs/alerts/10028/">Off-site Redirect</a></td>
                   <td><a href=""></a></td>
                </tr>
 

alerttags/owasp_2021_a03/index.xml

@@ -155,11 +155,11 @@
       <description>&lt;p&gt;MongoDB query injection may be possible.&lt;/p&gt;</description>
     </item>
     <item>
-      <title>Open Redirect</title>
+      <title>Off-site Redirect</title>
       <link>/docs/alerts/10028/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       <guid>/docs/alerts/10028/</guid>
-      <description>&lt;p&gt;Open redirects are one of the OWASP 2010 Top Ten vulnerabilities. This check looks at user-supplied input in query string parameters and POST data to identify where open redirects might be possible. Open redirects occur when an application allows user-supplied input (e.g. &lt;a href=&#34;https://nottrusted.com&#34;&gt;https://nottrusted.com&lt;/a&gt;) to control an offsite redirect. This is generally a pretty accurate way to find where 301 or 302 redirects could be exploited by spammers or phishing attacks.&lt;/p&gt;</description>
+      <description>&lt;p&gt;Open redirects are one of the OWASP 2010 Top Ten vulnerabilities. This check looks at user-supplied input in query string parameters and POST data to identify where open redirects might be possible. Open redirects occur when an application allows user-supplied input (e.g. &lt;a href=&#34;https://nottrusted.com&#34;&gt;https://nottrusted.com&lt;/a&gt;) to control an off-site destination. This is generally a pretty accurate way to find where 301 or 302 redirects could be exploited by spammers or phishing attacks.&lt;/p&gt;</description>
     </item>
     <item>
       <title>Out of Band XSS</title>

alerttags/policy_dev_std/index.html

@@ -350,7 +350,7 @@ <h4>POLICY_DEV_STD</h4>
 
 
                <tr>
-                  <td><a href="/docs/alerts/10028/">Open Redirect</a></td>
+                  <td><a href="/docs/alerts/10028/">Off-site Redirect</a></td>
                   <td><a href=""></a></td>
                </tr>
 

alerttags/policy_dev_std/index.xml

@@ -246,11 +246,11 @@
       <description>&lt;p&gt;The application appears to be a modern web application. If you need to explore it automatically then the Ajax Spider may well be more effective than the standard one.&lt;/p&gt;</description>
     </item>
     <item>
-      <title>Open Redirect</title>
+      <title>Off-site Redirect</title>
       <link>/docs/alerts/10028/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       <guid>/docs/alerts/10028/</guid>
-      <description>&lt;p&gt;Open redirects are one of the OWASP 2010 Top Ten vulnerabilities. This check looks at user-supplied input in query string parameters and POST data to identify where open redirects might be possible. Open redirects occur when an application allows user-supplied input (e.g. &lt;a href=&#34;https://nottrusted.com&#34;&gt;https://nottrusted.com&lt;/a&gt;) to control an offsite redirect. This is generally a pretty accurate way to find where 301 or 302 redirects could be exploited by spammers or phishing attacks.&lt;/p&gt;</description>
+      <description>&lt;p&gt;Open redirects are one of the OWASP 2010 Top Ten vulnerabilities. This check looks at user-supplied input in query string parameters and POST data to identify where open redirects might be possible. Open redirects occur when an application allows user-supplied input (e.g. &lt;a href=&#34;https://nottrusted.com&#34;&gt;https://nottrusted.com&lt;/a&gt;) to control an off-site destination. This is generally a pretty accurate way to find where 301 or 302 redirects could be exploited by spammers or phishing attacks.&lt;/p&gt;</description>
     </item>
     <item>
       <title>Path Traversal</title>

alerttags/policy_pentest/index.html

@@ -728,13 +728,13 @@ <h4>POLICY_PENTEST</h4>
 
 
                <tr>
-                  <td><a href="/docs/alerts/10032-3/">Old Asp.Net Version in Use</a></td>
+                  <td><a href="/docs/alerts/10028/">Off-site Redirect</a></td>
                   <td><a href=""></a></td>
                </tr>
 
 
                <tr>
-                  <td><a href="/docs/alerts/10028/">Open Redirect</a></td>
+                  <td><a href="/docs/alerts/10032-3/">Old Asp.Net Version in Use</a></td>
                   <td><a href=""></a></td>
                </tr>
 

alerttags/policy_pentest/index.xml

@@ -686,20 +686,20 @@
       <guid>/docs/alerts/10038-2/</guid>
       <description>&lt;p&gt;The &amp;ldquo;X-Content-Security-Policy&amp;rdquo; and &amp;ldquo;X-WebKit-CSP&amp;rdquo; headers are no longer recommended.&lt;/p&gt;</description>
     </item>
+    <item>
+      <title>Off-site Redirect</title>
+      <link>/docs/alerts/10028/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      <guid>/docs/alerts/10028/</guid>
+      <description>&lt;p&gt;Open redirects are one of the OWASP 2010 Top Ten vulnerabilities. This check looks at user-supplied input in query string parameters and POST data to identify where open redirects might be possible. Open redirects occur when an application allows user-supplied input (e.g. &lt;a href=&#34;https://nottrusted.com&#34;&gt;https://nottrusted.com&lt;/a&gt;) to control an off-site destination. This is generally a pretty accurate way to find where 301 or 302 redirects could be exploited by spammers or phishing attacks.&lt;/p&gt;</description>
+    </item>
     <item>
       <title>Old Asp.Net Version in Use</title>
       <link>/docs/alerts/10032-3/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       <guid>/docs/alerts/10032-3/</guid>
       <description>&lt;p&gt;This website uses ASP.NET version 1.0 or 1.1.&lt;/p&gt;</description>
     </item>
-    <item>
-      <title>Open Redirect</title>
-      <link>/docs/alerts/10028/</link>
-      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      <guid>/docs/alerts/10028/</guid>
-      <description>&lt;p&gt;Open redirects are one of the OWASP 2010 Top Ten vulnerabilities. This check looks at user-supplied input in query string parameters and POST data to identify where open redirects might be possible. Open redirects occur when an application allows user-supplied input (e.g. &lt;a href=&#34;https://nottrusted.com&#34;&gt;https://nottrusted.com&lt;/a&gt;) to control an offsite redirect. This is generally a pretty accurate way to find where 301 or 302 redirects could be exploited by spammers or phishing attacks.&lt;/p&gt;</description>
-    </item>
     <item>
       <title>Out of Band XSS</title>
       <link>/docs/alerts/40031/</link>