<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>OWASP_2025_A06 on ZAP</title>
    <link>/alerttags/owasp_2025_a06/</link>
    <description>Recent content in OWASP_2025_A06 on ZAP</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="/alerttags/owasp_2025_a06/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Big Redirect Detected (Potential Sensitive Information Leak)</title>
      <link>/docs/alerts/10044-1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/10044-1/</guid>
      <description>&lt;p&gt;The server has responded with a redirect that seems to provide a large response. This may indicate that although the server sent a redirect it also responded with body content (which may include sensitive details, PII, etc.).&lt;/p&gt;</description>
    </item>
    <item>
      <title>Cross-Origin-Embedder-Policy Header Missing or Invalid</title>
      <link>/docs/alerts/90004-2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/90004-2/</guid>
      <description>&lt;p&gt;Cross-Origin-Embedder-Policy header is a response header that prevents a document from loading any cross-origin resources that don&amp;rsquo;t explicitly grant the document permission (using CORP or CORS).&lt;/p&gt;</description>
    </item>
    <item>
      <title>Cross-Origin-Opener-Policy Header Missing or Invalid</title>
      <link>/docs/alerts/90004-3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/90004-3/</guid>
      <description>&lt;p&gt;Cross-Origin-Opener-Policy header is a response header that allows a site to control if others included documents share the same browsing context. Sharing the same browsing context with untrusted documents might lead to data leak.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Cross-Origin-Resource-Policy Header Missing or Invalid</title>
      <link>/docs/alerts/90004-1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/90004-1/</guid>
      <description>&lt;p&gt;Cross-Origin-Resource-Policy header is an opt-in header designed to counter side-channels attacks like Spectre. Resource should be specifically set as shareable amongst different origins.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Dangerous JS Functions</title>
      <link>/docs/alerts/10110/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/10110/</guid>
      <description>&lt;p&gt;A dangerous JS function seems to be in use that would leave the site vulnerable.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Emails Found in the Viewstate</title>
      <link>/docs/alerts/10032-2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/10032-2/</guid>
      <description>&lt;p&gt;Email addresses were found being serialized in the viewstate field.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Exponential Entity Expansion (Billion Laughs Attack)</title>
      <link>/docs/alerts/40044/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/40044/</guid>
      <description>&lt;p&gt;An exponential entity expansion, or &amp;ldquo;billion laughs&amp;rdquo; attack is a type of denial-of-service (DoS) attack. It is aimed at parsers of markup languages like XML or YAML that allow macro expansions.&lt;/p&gt;</description>
    </item>
    <item>
      <title>GET for POST</title>
      <link>/docs/alerts/10058/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/10058/</guid>
      <description>&lt;p&gt;A request that was originally observed as a POST was also accepted as a GET. This issue does not represent a security weakness unto itself, however, it may facilitate simplification of other attacks. For example if the original POST is subject to Cross-Site Scripting (XSS), then this finding may indicate that a simplified (GET based) XSS may also be possible.&lt;/p&gt;</description>
    </item>
    <item>
      <title>GraphQL Circular Type Reference</title>
      <link>/docs/alerts/50007-3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/50007-3/</guid>
      <description>&lt;p&gt;A circular reference was detected in the GraphQL schema, where object types reference each other in a cycle. This can be exploited by attackers to craft deeply recursive queries, potentially leading to Denial of Service (DoS) conditions.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Hash Disclosure - MD4 / MD5</title>
      <link>/docs/alerts/10097/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/10097/</guid>
      <description>&lt;p&gt;A hash was disclosed by the web server. - MD4 / MD5&lt;/p&gt;</description>
    </item>
    <item>
      <title>HTTP Parameter Override</title>
      <link>/docs/alerts/10026/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/10026/</guid>
      <description>&lt;p&gt;Unspecified form action: HTTP parameter override attack potentially possible. This is a known problem with Java Servlets but other platforms may also be vulnerable.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Insecure JSF ViewState</title>
      <link>/docs/alerts/90001/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/90001/</guid>
      <description>&lt;p&gt;The response at the following URL contains a ViewState value that has no cryptographic protections.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Java Serialization Object</title>
      <link>/docs/alerts/90002/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/90002/</guid>
      <description>&lt;p&gt;Java Serialization seems to be in use. If not correctly validated, an attacker can send a specially crafted object. This can lead to a dangerous &amp;ldquo;Remote Code Execution&amp;rdquo;. A magic sequence identifying JSO has been detected (Base64: rO0AB, Raw: 0xac, 0xed, 0x00, 0x05).&lt;/p&gt;</description>
    </item>
    <item>
      <title>Multiple HREFs Redirect Detected (Potential Sensitive Information Leak)</title>
      <link>/docs/alerts/10044-2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/10044-2/</guid>
      <description>&lt;p&gt;The server has responded with a redirect that seems to contain multiple links. This may indicate that although the server sent a redirect it also responded with body content links (which may include sensitive details, PII, lead to admin panels, etc.).&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>Parameter Tampering</title>
      <link>/docs/alerts/40008/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/40008/</guid>
      <description>&lt;p&gt;Parameter manipulation caused an error page or Java stack trace to be displayed. This indicated lack of exception handling and potential areas for further exploit.&lt;/p&gt;</description>
    </item>
    <item>
      <title>PII Disclosure</title>
      <link>/docs/alerts/10062/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/10062/</guid>
      <description>&lt;p&gt;The response contains Personally Identifiable Information, such as CC number, SSN and similar sensitive data.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Potential IP Addresses Found in the Viewstate</title>
      <link>/docs/alerts/10032-1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/10032-1/</guid>
      <description>&lt;p&gt;Potential IP addresses were found being serialized in the viewstate field.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Reverse Tabnabbing</title>
      <link>/docs/alerts/10108/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/10108/</guid>
      <description>&lt;p&gt;At least one link on this page is vulnerable to Reverse tabnabbing as it uses a target attribute without using both of the &amp;ldquo;noopener&amp;rdquo; and &amp;ldquo;noreferrer&amp;rdquo; keywords in the &amp;ldquo;rel&amp;rdquo; attribute, which allows the target page to take control of this page.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Split Viewstate in Use</title>
      <link>/docs/alerts/10032-6/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/10032-6/</guid>
      <description>&lt;p&gt;This website uses ASP.NET&amp;rsquo;s Viewstate and its value is split into several chunks.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Viewstate without MAC Signature (Sure)</title>
      <link>/docs/alerts/10032-5/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/10032-5/</guid>
      <description>&lt;p&gt;This website uses ASP.NET&amp;rsquo;s Viewstate but without any MAC.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Viewstate without MAC Signature (Unsure)</title>
      <link>/docs/alerts/10032-4/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/10032-4/</guid>
      <description>&lt;p&gt;This website uses ASP.NET&amp;rsquo;s Viewstate but maybe without any MAC.&lt;/p&gt;</description>
    </item>
    <item>
      <title>X-ChromeLogger-Data (XCOLD) Header Information Leak</title>
      <link>/docs/alerts/10052/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/10052/</guid>
      <description>&lt;p&gt;The server is leaking information through the X-ChromeLogger-Data (or X-ChromePhp-Data) response header. The content of such headers can be customized by the developer, however it is not uncommon to find: server file system locations, vhost declarations, etc.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
