<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>War Room</title>
	<atom:link href="https://warroom.rsmus.com/tag/vuln-box/feed/" rel="self" type="application/rss+xml" />
	<link>https://warroom.rsmus.com</link>
	<description>Shells From Above</description>
	<lastBuildDate>Thu, 15 Feb 2024 19:26:15 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://warroom.rsmus.com/wp-content/uploads/2018/09/cropped-favicon-32x32.png</url>
	<title>War Room</title>
	<link>https://warroom.rsmus.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Building a Lab Network in Proxmox and Sophos UTM9</title>
		<link>https://warroom.rsmus.com/building-a-lab-network-in-proxmox/</link>
		
		<dc:creator><![CDATA[Ken Smith]]></dc:creator>
		<pubDate>Mon, 13 Jul 2020 16:15:58 +0000</pubDate>
				<category><![CDATA[Defense]]></category>
		<category><![CDATA[Offense]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[Proxmox]]></category>
		<category><![CDATA[Sophos]]></category>
		<category><![CDATA[Tutorial]]></category>
		<category><![CDATA[UTM]]></category>
		<category><![CDATA[Virtual Machine]]></category>
		<category><![CDATA[Vuln Box]]></category>
		<guid isPermaLink="false">https://warroom.rsmus.com/?p=5180</guid>

					<description><![CDATA[One of the best ways to acquire and maintain an offensive security skill set is to build a home lab and populate it with intentionally vulnerable machines. The most straightforward option is to simply spin up VMs in VirtualBox or VMWare Player and manage everything locally. To take things to the next level, however, you [&#8230;]]]></description>
		
		
		
			</item>
		<item>
		<title>Building a Vulnerable Box &#8211; HFS Revisted</title>
		<link>https://warroom.rsmus.com/building-a-vulnerable-box-hfs-revisited/</link>
		
		<dc:creator><![CDATA[Ken Smith]]></dc:creator>
		<pubDate>Mon, 31 Aug 2015 19:52:11 +0000</pubDate>
				<category><![CDATA[Offense]]></category>
		<category><![CDATA[Attack]]></category>
		<category><![CDATA[Exploit]]></category>
		<category><![CDATA[Exploit-DB]]></category>
		<category><![CDATA[FHFS]]></category>
		<category><![CDATA[HFS]]></category>
		<category><![CDATA[Rejetto]]></category>
		<category><![CDATA[Vuln Box]]></category>
		<guid isPermaLink="false">https://warroom.rsmus.com/?p=1573</guid>

					<description><![CDATA[A few months ago, in the Building a Vulnerable Box series, I wrote a walkthrough for putting together and compromising a Rejetto HFS server. The post had originally been intended for my security students at the time, but, to my surprise, it&#8217;s become one of the War Room&#8217;s most consistently visited write-ups. Just last week, a similar exploit was [&#8230;]]]></description>
		
		
		
			</item>
		<item>
		<title>Building a Vulnerable Box &#8211; Heartbleed</title>
		<link>https://warroom.rsmus.com/building-a-vulnerable-box-heartbleed/</link>
		
		<dc:creator><![CDATA[RSM Author]]></dc:creator>
		<pubDate>Fri, 22 May 2015 13:52:34 +0000</pubDate>
				<category><![CDATA[Offense]]></category>
		<category><![CDATA[Attack]]></category>
		<category><![CDATA[Heartbleed]]></category>
		<category><![CDATA[Metasploit]]></category>
		<category><![CDATA[Penetration Testing]]></category>
		<category><![CDATA[Tutorial]]></category>
		<category><![CDATA[Vuln Box]]></category>
		<guid isPermaLink="false">https://warroom.rsmus.com/?p=1092</guid>

					<description><![CDATA[Patchwork may have wrapped this series up in his last post, but I&#8217;ve got one more to add. The Heartbleed bug (CVE-2014-0160) received a lot of press when it was discovered and disclosed in April of 2014, and deservedly so.  The vulnerability was severe not only because of the sensitivity of the information it could leak, [&#8230;]]]></description>
		
		
		
			</item>
		<item>
		<title>Building a Vulnerable Box &#8211; Domino</title>
		<link>https://warroom.rsmus.com/building-a-vulnerable-box-domino/</link>
		
		<dc:creator><![CDATA[Ken Smith]]></dc:creator>
		<pubDate>Tue, 21 Apr 2015 16:59:15 +0000</pubDate>
				<category><![CDATA[Offense]]></category>
		<category><![CDATA[Attack]]></category>
		<category><![CDATA[Build]]></category>
		<category><![CDATA[Domino]]></category>
		<category><![CDATA[Exploit]]></category>
		<category><![CDATA[Lotus]]></category>
		<category><![CDATA[Lotus Notes]]></category>
		<category><![CDATA[NSF]]></category>
		<category><![CDATA[Penetration Testing]]></category>
		<category><![CDATA[Vuln Box]]></category>
		<guid isPermaLink="false">https://warroom.rsmus.com/?p=872</guid>

					<description><![CDATA[IBM Domino  (formerly Lotus Domino) is a particular interesting (and lengthy) setup. The build is not terribly complicated, but the software has been vulnerable for a long time, so it&#8217;s definitely worth exploring. We might as well have titled the blog &#8220;Building a Domino Box&#8221; with the vulnerability simply assumed. This box was also featured on [&#8230;]]]></description>
		
		
		
			</item>
	</channel>
</rss>
