<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>browser on Hackropole</title>
    <link>https://hackropole.fr/en/browser/</link>
    <description>Recent content in browser on Hackropole</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 03 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://hackropole.fr/en/browser/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Spidersaurus</title>
      <link>https://hackropole.fr/en/challenges/pwn/fcsc2026-pwn-spidersaurus/</link>
      <pubDate>Mon, 13 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://hackropole.fr/en/challenges/pwn/fcsc2026-pwn-spidersaurus/</guid>
      <description>&lt;p&gt;After a few hiccups with the &lt;a href=&#34;https://hackropole.fr/en/challenges/pwn/fcsc2023-pwn-may-the-forth/&#34;&gt;FORTH&lt;/a&gt; language, as well as the &lt;a href=&#34;https://hackropole.fr/fr/challenges/pwn/fcsc2025-pwn-back-to-basic/&#34;&gt;BASIC&lt;/a&gt; language, our developper has decided to get back to the roots of the multimedia Internet with the help of a JavaScript interpreter, &lt;a href=&#34;https://ftp.mozilla.org/pub/mozilla/source/mozilla-19980603.tar.gz&#34;&gt;SpiderMoney 1.3&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;He assures us that no security vulnerability is exploitable, thanks to compilation flags; furthermore, he guarantees the code is safe from the Y2K bug.&lt;/p&gt;&#xA;&lt;p&gt;However, an anonymous hacker has sent us an enigmatic file &lt;code&gt;test.js&lt;/code&gt; which seems to trigger the read of uninitialized memory. Can you prove our developer wrong by reading the contents of the flag variable?&lt;/p&gt;</description>
    </item>
    <item>
      <title>Spidersaurus Rex</title>
      <link>https://hackropole.fr/en/challenges/pwn/fcsc2026-pwn-spidersaurus-rex/</link>
      <pubDate>Mon, 13 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://hackropole.fr/en/challenges/pwn/fcsc2026-pwn-spidersaurus-rex/</guid>
      <description>&lt;p&gt;Despite a memory access problem (see the Spidersaurus challenge), our developer insists on using this ancient version of SpiderMonkey.&lt;/p&gt;&#xA;&lt;p&gt;He keeps assuring us there are no exploitable security flaws. However, an anonymous hacker sent us this mysterious message: &amp;ldquo;what happens if a function contains &lt;a href=&#34;https://github.com/ehsan/mozilla-cvs-history/commit/e3ba7ebdb650&#34;&gt;65536 variables&lt;/a&gt;?&amp;rdquo;. Show our developer wrong by reading the contents of &lt;code&gt;flag.txt&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;After sending your JavaScript code, use &lt;em&gt;shutdown(socket, SHUT_WR)&lt;/em&gt; to trigger its execution, and then read the potential response.&lt;/li&gt;&#xA;&lt;li&gt;A JavaScript string can contain arbitrary binary content, for instance \u9090\u9090.&lt;/li&gt;&#xA;&lt;li&gt;The memory allocation pattern will differ if the JavaScript code is provided as a file with the first argument, instead of using &lt;em&gt;stdin&lt;/em&gt;.&lt;/li&gt;&#xA;&lt;/ol&gt;</description>
    </item>
    <item>
      <title>Holy Cow</title>
      <link>https://hackropole.fr/en/challenges/pwn/fcsc2024-pwn-holy-cow/</link>
      <pubDate>Mon, 15 Apr 2024 00:00:00 +0000</pubDate>
      <guid>https://hackropole.fr/en/challenges/pwn/fcsc2024-pwn-holy-cow/</guid>
      <description>&lt;p&gt;Our adventure began, as is often the case with this kind of project, with a chat over a drink. All more tipsy than the last, but with a common resolution: &amp;ldquo;Let&amp;rsquo;s make our own web browser!&amp;rdquo;.&lt;/p&gt;&#xA;&lt;p&gt;Once half sobered up, we decided to start by choosing the right Javascript engine. The V8 engine is our first choice, as it has the advantage of being &lt;em&gt;open source&lt;/em&gt;.&#xA;Your task today is to check, using the &lt;code&gt;git patch&lt;/code&gt; and the supplied executable, that everything is in order.&#xA;To solve the challenge, we need to read the &lt;code&gt;flag.txt&lt;/code&gt; file.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
