<?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>HTB on s4yhii&#39;s blog</title>
    <link>https://blog.s4yhii.com/categories/htb/</link>
    <description>Recent content in HTB on s4yhii&#39;s blog</description>
    <image>
      <title>s4yhii&#39;s blog</title>
      <url>https://blog.s4yhii.com/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</url>
      <link>https://blog.s4yhii.com/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</link>
    </image>
    <generator>Hugo -- 0.155.3</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 10 Feb 2024 12:00:00 -0400</lastBuildDate>
    <atom:link href="https://blog.s4yhii.com/categories/htb/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Web Cache Poisoning Techniques</title>
      <link>https://blog.s4yhii.com/posts/2024-02-10-web-cache-poisoning/</link>
      <pubDate>Sat, 10 Feb 2024 12:00:00 -0400</pubDate>
      <guid>https://blog.s4yhii.com/posts/2024-02-10-web-cache-poisoning/</guid>
      <description>&lt;h1 id=&#34;web-cache-poisoning&#34;&gt;Web cache Poisoning&lt;/h1&gt;
&lt;p&gt;Web cache poisoning is not web cache deception, is not response splitting or request smuggling
web cache deception tricking caches into storing sensitive information so the attackers can access to it.
web cache poisoning is serve payloads to users via cache responses
&lt;img loading=&#34;lazy&#34; src=&#34;https://raw.githubusercontent.com/s4yhii/s4yhii.github.io/master/assets/images/wcp/Pasted%20image%2020231126235320.png&#34;&gt;&lt;/p&gt;
&lt;p&gt;Cache keys: The unique identifier that the server wont cache (refresh based on that: only host + path)
&lt;img loading=&#34;lazy&#34; src=&#34;https://raw.githubusercontent.com/s4yhii/s4yhii.github.io/master/assets/images/wcp/Pasted%20image%2020231126235920.png&#34;&gt;&lt;/p&gt;
&lt;p&gt;&amp;ldquo;Everything that is not part of the cache key is part of the cache poisoning attack surface&amp;rdquo;&lt;/p&gt;</description>
    </item>
    <item>
      <title>HackTheBox Web Challenges</title>
      <link>https://blog.s4yhii.com/posts/2022-07-01-web-challenges-htb/</link>
      <pubDate>Fri, 01 Jul 2022 12:00:00 -0400</pubDate>
      <guid>https://blog.s4yhii.com/posts/2022-07-01-web-challenges-htb/</guid>
      <description>&lt;h1 id=&#34;templated&#34;&gt;Templated&lt;/h1&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://raw.githubusercontent.com/s4yhii/s4yhii.github.io/master/assets/images/htb/challenges/ch0.jpg&#34;&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Dificulty: easy&lt;/li&gt;
&lt;li&gt;Description: Can you exploit this simple mistake?&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;solution&#34;&gt;Solution&lt;/h2&gt;
&lt;p&gt;First we visit the site and see that uses jinja2, this template is susceptible to &lt;code&gt;SSTI attacks&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://raw.githubusercontent.com/s4yhii/s4yhii.github.io/master/assets/images/htb/challenges/ch1.jpg&#34;&gt;&lt;/p&gt;
&lt;p&gt;We see that the directory searched is rendered in the page with 25, so its vulnerable to SSTI.&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://raw.githubusercontent.com/s4yhii/s4yhii.github.io/master/assets/images/htb/challenges/ch2.jpg&#34;&gt;&lt;/p&gt;
&lt;p&gt;We use the payload that will allow us to &lt;code&gt;RCE&lt;/code&gt; on the server to read the file &lt;code&gt;flag.txt&lt;/code&gt;, we extract it from &lt;a href=&#34;https://github.com/swisskyrepo/PayloadsAllTheThings/blob/master/Server%20Side%20Template%20Injection/README.md#jinja2---remote-code-execution&#34;&gt;PayloadsAllTheThings&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
