<?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>exploitation &#8211; SCRT Team Blog</title>
	<atom:link href="/tag/exploitation/feed/" rel="self" type="application/rss+xml" />
	<link>/</link>
	<description>Orange Cyberdefense Switzerland&#039;s technical blog</description>
	<lastBuildDate>Thu, 12 Jan 2023 14:27:31 +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>/wp-content/uploads/2024/10/cropped-favicon-32x32-1-32x32.png</url>
	<title>exploitation &#8211; SCRT Team Blog</title>
	<link>/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Insomni&#8217;hack 2013 Armory level1 &#038; level2</title>
		<link>/2013/04/04/insomnihack-2013-armory-level1-level2/</link>
		
		<dc:creator><![CDATA[blogscrt]]></dc:creator>
		<pubDate>Thu, 04 Apr 2013 11:47:45 +0000</pubDate>
				<category><![CDATA[Insomni'hack]]></category>
		<category><![CDATA[arm]]></category>
		<category><![CDATA[exploitation]]></category>
		<category><![CDATA[raspberrypi]]></category>
		<guid isPermaLink="false">/?p=1155</guid>

					<description><![CDATA[Level1 should be pretty straightforward. Looking at the assenbly, you can see that it prints the current working directory by using system(&#8220;pwd&#8221;) and then strcpy user controlled data to a fixed size buffer. Stack is NX so we need to ret2libc, pretty easy here as the address of system is known inside the binary: So, &#8230; <a href="/2013/04/04/insomnihack-2013-armory-level1-level2/" class="more-link">Continue reading <span class="screen-reader-text">Insomni&#8217;hack 2013 Armory level1 &#38; level2</span></a>]]></description>
		
		
		
			</item>
		<item>
		<title>Vulnérabilités &#8220;old school&#8221;</title>
		<link>/2010/08/25/vulnerabilites-old-school/</link>
					<comments>/2010/08/25/vulnerabilites-old-school/#respond</comments>
		
		<dc:creator><![CDATA[blogscrt]]></dc:creator>
		<pubDate>Wed, 25 Aug 2010 21:13:03 +0000</pubDate>
				<category><![CDATA[Vulnerability]]></category>
		<category><![CDATA[exploitation]]></category>
		<category><![CDATA[Vulnérabilité]]></category>
		<guid isPermaLink="false">/?p=107</guid>

					<description><![CDATA[En regardant les titres des présentations des conférences de sécurité ou les articles traitants de JIT-Spraying et ROP on pourrait penser que pour exécuter du code sur une machine ou élever ses privilèges il faut déployer des techniques de plus en plus complexes. Ce raisonnement est correct à la vue des protections comme l&#8217;ASLR, DEP, &#8230; <a href="/2010/08/25/vulnerabilites-old-school/" class="more-link">Continue reading <span class="screen-reader-text">Vulnérabilités &#8220;old school&#8221;</span></a>]]></description>
		
					<wfw:commentRss>/2010/08/25/vulnerabilites-old-school/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
