<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>CWE-352 on ZAP</title>
    <link>/alerttags/cwe-352/</link>
    <description>Recent content in CWE-352 on ZAP</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="/alerttags/cwe-352/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Absence of Anti-CSRF Tokens</title>
      <link>/docs/alerts/10202/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/10202/</guid>
      <description>&lt;p&gt;No Anti-CSRF tokens were found in a HTML submission form.&#xA;A cross-site request forgery is an attack that involves forcing a victim to send an HTTP request to a target destination without their knowledge or intent in order to perform an action as the victim. The underlying cause is application functionality using predictable URL/form actions in a repeatable way. The nature of the attack is that CSRF exploits the trust that a web site has for a user. By contrast, cross-site scripting (XSS) exploits the trust that a user has for a web site. Like XSS, CSRF attacks are not necessarily cross-site, but they can be. Cross-site request forgery is also known as CSRF, XSRF, one-click attack, session riding, confused deputy, and sea surf.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Anti-CSRF Tokens Check</title>
      <link>/docs/alerts/20012/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/20012/</guid>
      <description>&lt;p&gt;A cross-site request forgery is an attack that involves forcing a victim to send an HTTP request to a target destination without their knowledge or intent in order to perform an action as the victim. The underlying cause is application functionality using predictable URL/form actions in a repeatable way. The nature of the attack is that CSRF exploits the trust that a web site has for a user. By contrast, cross-site scripting (XSS) exploits the trust that a user has for a web site. Like XSS, CSRF attacks are not necessarily cross-site, but they can be. Cross-site request forgery is also known as CSRF, XSRF, one-click attack, session riding, confused deputy, and sea surf.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Cross Site Request Forgery</title>
      <link>/docs/alerts/40103/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/40103/</guid>
      <description>&lt;p&gt;A cross-site request forgery is an attack that involves forcing a victim to send an HTTP request to a target destination without their knowledge or intent in order to perform an action as the victim. The underlying cause is application functionality using predictable URL/form actions in a repeatable way. The nature of the attack is that CSRF exploits the trust that a web site has for a user. By contrast, cross-site scripting (XSS) exploits the trust that a user has for a web site. Like XSS, CSRF attacks are not necessarily cross-site, but they can be. Cross-site request forgery is also known as CSRF, XSRF, one-click attack, session riding, confused deputy, and sea surf.&lt;/p&gt;</description>
    </item>
    <item>
      <title>SameSite Cookie Attribute Protection Used</title>
      <link>/docs/alerts/100005/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/100005/</guid>
      <description></description>
    </item>
    <item>
      <title>Sec-Fetch-Dest Header Has an Invalid Value</title>
      <link>/docs/alerts/90005-7/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/90005-7/</guid>
      <description>&lt;p&gt;Specifies how and where the data would be used. For instance, if the value is audio, then the requested resource must be audio data and not any other type of resource.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Sec-Fetch-Dest Header is Missing</title>
      <link>/docs/alerts/90005-3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/90005-3/</guid>
      <description>&lt;p&gt;Specifies how and where the data would be used. For instance, if the value is audio, then the requested resource must be audio data and not any other type of resource.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Sec-Fetch-Mode Header Has an Invalid Value</title>
      <link>/docs/alerts/90005-6/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/90005-6/</guid>
      <description>&lt;p&gt;Allows to differentiate between requests for navigating between HTML pages and requests for loading resources like images, audio etc.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Sec-Fetch-Mode Header is Missing</title>
      <link>/docs/alerts/90005-2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/90005-2/</guid>
      <description>&lt;p&gt;Allows to differentiate between requests for navigating between HTML pages and requests for loading resources like images, audio etc.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Sec-Fetch-Site Header Has an Invalid Value</title>
      <link>/docs/alerts/90005-5/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/90005-5/</guid>
      <description>&lt;p&gt;Specifies the relationship between request initiator&amp;rsquo;s origin and target&amp;rsquo;s origin.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Sec-Fetch-Site Header is Missing</title>
      <link>/docs/alerts/90005-1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/90005-1/</guid>
      <description>&lt;p&gt;Specifies the relationship between request initiator&amp;rsquo;s origin and target&amp;rsquo;s origin.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Sec-Fetch-User Header Has an Invalid Value</title>
      <link>/docs/alerts/90005-8/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/90005-8/</guid>
      <description>&lt;p&gt;Specifies if a navigation request was initiated by a user.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Sec-Fetch-User Header is Missing</title>
      <link>/docs/alerts/90005-4/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/90005-4/</guid>
      <description>&lt;p&gt;Specifies if a navigation request was initiated by a user.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
