<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Qemu on Tyler's Blog</title><link>https://blog.zars.me/tags/qemu/</link><description>Recent content in Qemu on Tyler's Blog</description><generator>Hugo</generator><language>en-us</language><copyright>© Athul</copyright><lastBuildDate>Sat, 27 Apr 2024 12:13:32 +0530</lastBuildDate><atom:link href="https://blog.zars.me/tags/qemu/index.xml" rel="self" type="application/rss+xml"/><item><title>hitb-gsec-2017 babyqemu</title><link>https://blog.zars.me/posts/hitb-gsec-2017/</link><pubDate>Sat, 27 Apr 2024 12:13:32 +0530</pubDate><guid>https://blog.zars.me/posts/hitb-gsec-2017/</guid><description>This was an old challenge, but one of my friends was teaching to it and I knew nothing about QEMU and physical hardware. I went into it know it was a QEMU escape so I won&amp;rsquo;t be covering the mindset of finding that out but I&amp;rsquo;ll break down the indepth meaning behind what the exploit does and some of the QEMU internals that make this problem solvable.
The Problem The provided resources for the challenge allude to it being a QEMU challenge:</description></item></channel></rss>