<?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>Cookies on Akshit Kathuria</title>
    <link>https://ak-debug.github.io/tags/cookies/</link>
    <description>Recent content in Cookies on Akshit Kathuria</description>
    <image>
      <title>Akshit Kathuria</title>
      <url>https://ak-debug.github.io/social-preview.png</url>
      <link>https://ak-debug.github.io/social-preview.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 12 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://ak-debug.github.io/tags/cookies/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Broken Access Control: IDOR and Cookie Tampering</title>
      <link>https://ak-debug.github.io/posts/broken-access-control-idor-and-cookies/</link>
      <pubDate>Thu, 12 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://ak-debug.github.io/posts/broken-access-control-idor-and-cookies/</guid>
      <description>When the server trusts a value the client can change to decide who you are or what you can see, you can often just change it. Here I cover two sides of broken access control: tampering with a client-side cookie to become an admin, and incrementing an ID in the URL to read someone else&amp;rsquo;s record, using two DD CTF challenges as worked examples.</description>
    </item>
  </channel>
</rss>
