<?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_A07 on ZAP</title>
    <link>/alerttags/owasp_2025_a07/</link>
    <description>Recent content in OWASP_2025_A07 on ZAP</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="/alerttags/owasp_2025_a07/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Authentication Credentials Captured</title>
      <link>/docs/alerts/10105-1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/10105-1/</guid>
      <description>&lt;p&gt;An insecure authentication mechanism is in use. This allows an attacker on the network access to the userid and password of the authenticated user. For Basic Authentication, the attacker must merely monitor the network traffic until a Basic Authentication request is received, and then base64 decode the username and password. For Digest Authentication, the attacker has access to the username, and possibly also the password, if the hash (including a nonce) can be successfully cracked, or if a Man-In-The-Middle attack is mounted.&#xA;The attacker eavesdrops on the network until an authentication has completed.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Non-Storable Content</title>
      <link>/docs/alerts/10049-1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/10049-1/</guid>
      <description>&lt;p&gt;The response contents are not storable by caching components such as proxy servers. If the response does not contain sensitive, personal or user-specific information, it may benefit from being stored and cached, to improve performance.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Re-examine Cache-control Directives</title>
      <link>/docs/alerts/10015/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/10015/</guid>
      <description>&lt;p&gt;The cache-control header has not been set properly or is missing, allowing the browser and proxies to cache content. For static assets like css, js, or image files this might be intended, however, the resources should be reviewed to ensure that no sensitive content will be cached.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Retrieved from Cache</title>
      <link>/docs/alerts/10050-1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/10050-1/</guid>
      <description>&lt;p&gt;The content was retrieved from a shared cache. If the response data is sensitive, personal or user-specific, this may result in sensitive information being leaked. In some cases, this may even result in a user gaining complete control of the session of another user, depending on the configuration of the caching components in use in their environment. This is primarily an issue where caching servers such as &amp;ldquo;proxy&amp;rdquo; caches are configured on the local network. This configuration is typically found in corporate or educational environments, for instance.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Retrieved from Cache</title>
      <link>/docs/alerts/10050-2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/10050-2/</guid>
      <description>&lt;p&gt;The content was retrieved from a shared cache. If the response data is sensitive, personal or user-specific, this may result in sensitive information being leaked. In some cases, this may even result in a user gaining complete control of the session of another user, depending on the configuration of the caching components in use in their environment. This is primarily an issue where caching servers such as &amp;ldquo;proxy&amp;rdquo; caches are configured on the local network. This configuration is typically found in corporate or educational environments, for instance.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Storable and Cacheable Content</title>
      <link>/docs/alerts/10049-3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/10049-3/</guid>
      <description>&lt;p&gt;The response contents are storable by caching components such as proxy servers, and may be retrieved directly from the cache, rather than from the origin server by the caching servers, in response to similar requests from other users. If the response data is sensitive, personal or user-specific, this may result in sensitive information being leaked. In some cases, this may even result in a user gaining complete control of the session of another user, depending on the configuration of the caching components in use in their environment. This is primarily an issue where &amp;ldquo;shared&amp;rdquo; caching servers such as &amp;ldquo;proxy&amp;rdquo; caches are configured on the local network. This configuration is typically found in corporate or educational environments, for instance.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Storable but Non-Cacheable Content</title>
      <link>/docs/alerts/10049-2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/10049-2/</guid>
      <description>&lt;p&gt;The response contents are storable by caching components such as proxy servers, but will not be retrieved directly from the cache, without validating the request upstream, in response to similar requests from other users.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Weak Authentication Method</title>
      <link>/docs/alerts/10105-2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/10105-2/</guid>
      <description>&lt;p&gt;HTTP basic or digest authentication has been used over an unsecured connection. The credentials can be read and then reused by someone with access to the network.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
