<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Session Attacks on MrAzoth</title>
    <link>https://az0th.it/web/session/</link>
    <description>Recent content in Session Attacks on MrAzoth</description>
    <generator>Hugo -- 0.154.5</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 24 Feb 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://az0th.it/web/session/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Session Fixation</title>
      <link>https://az0th.it/web/session/040-session-fixation/</link>
      <pubDate>Tue, 24 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://az0th.it/web/session/040-session-fixation/</guid>
      <description>&lt;h1 id=&#34;session-fixation&#34;&gt;Session Fixation&lt;/h1&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Severity&lt;/strong&gt;: High | &lt;strong&gt;CWE&lt;/strong&gt;: CWE-384
&lt;strong&gt;OWASP&lt;/strong&gt;: A07:2021 – Identification and Authentication Failures&lt;/p&gt;
&lt;/blockquote&gt;
&lt;hr&gt;
&lt;h2 id=&#34;what-is-session-fixation&#34;&gt;What Is Session Fixation?&lt;/h2&gt;
&lt;p&gt;Session fixation occurs when an application does not issue a &lt;strong&gt;new session identifier after successful authentication&lt;/strong&gt;. An attacker who can set or predict the victim&amp;rsquo;s pre-authentication session ID can then wait for the victim to log in and immediately reuse that same ID to gain authenticated access.&lt;/p&gt;
&lt;p&gt;The classic scenario requires the attacker to be able to push a known session ID to the victim — via URL parameter, cookie injection, or subdomain cookie injection.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Session Puzzling / Session Variable Overloading</title>
      <link>https://az0th.it/web/session/041-session-puzzling/</link>
      <pubDate>Tue, 24 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://az0th.it/web/session/041-session-puzzling/</guid>
      <description>&lt;h1 id=&#34;session-puzzling--session-variable-overloading&#34;&gt;Session Puzzling / Session Variable Overloading&lt;/h1&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Severity&lt;/strong&gt;: High | &lt;strong&gt;CWE&lt;/strong&gt;: CWE-384, CWE-613
&lt;strong&gt;OWASP&lt;/strong&gt;: A07:2021 – Identification and Authentication Failures&lt;/p&gt;
&lt;/blockquote&gt;
&lt;hr&gt;
&lt;h2 id=&#34;what-is-session-puzzling&#34;&gt;What Is Session Puzzling?&lt;/h2&gt;
&lt;p&gt;Session Puzzling (also called Session Variable Overloading) is a vulnerability where the same session variable is used for different purposes in different application contexts, and an attacker can exploit this reuse to bypass authentication or authorization controls.&lt;/p&gt;
&lt;p&gt;The core issue: when the same key in the session store holds different semantic meaning depending on which workflow put it there, an attacker can use one workflow to set a value that satisfies the check in another workflow.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
