<?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>Angels of security &#187; Microsoft</title>
	<atom:link href="http://angelsofsecurity.com/blog/tag/microsoft/feed/" rel="self" type="application/rss+xml" />
	<link>http://angelsofsecurity.com/blog</link>
	<description>Musings of an infosec renegade</description>
	<lastBuildDate>Tue, 02 Aug 2011 19:01:53 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Windows 7 firewall and IPv6</title>
		<link>http://angelsofsecurity.com/blog/2010/03/11/windows-7-firewall-and-ipv6/</link>
		<comments>http://angelsofsecurity.com/blog/2010/03/11/windows-7-firewall-and-ipv6/#comments</comments>
		<pubDate>Thu, 11 Mar 2010 19:32:05 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Access Control Systems & Methodology]]></category>
		<category><![CDATA[firewall]]></category>
		<category><![CDATA[ipv6]]></category>
		<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[windows]]></category>
		<category><![CDATA[windows 7]]></category>

		<guid isPermaLink="false">http://angelsofsecurity.com/blog/?p=564</guid>
		<description><![CDATA[Another random Windows 7 fact I learned today &#8211; if you disable the Windows 7 firewall, it will also disable IPV6 and Service Hardening. Microsoft&#8217;s logic appears to be simply that if a system doesn&#8217;t have the Windows firewall enabled, then it should be treated as an insecure machine and not trusted to connect with [...]]]></description>
			<content:encoded><![CDATA[<p>Another random Windows 7 fact I learned today &#8211; if you disable the Windows 7 firewall, it will also disable IPV6 and <a href="http://blogs.technet.com/askperf/archive/2008/02/03/ws2008-windows-service-hardening.aspx">Service Hardening</a>. Microsoft&#8217;s logic appears to be simply that if a system doesn&#8217;t have the Windows firewall enabled, then it should be treated as an insecure machine and not trusted to connect with an IPV6 IPSec tunnel. The obvious flaw in this logic is that many enterprises use other firewalls, which Windows will not account for. Those people will then have ot enable the Microsoft firewall and just put it into a completely accepting state if they want to use IPV6.</p>
]]></content:encoded>
			<wfw:commentRss>http://angelsofsecurity.com/blog/2010/03/11/windows-7-firewall-and-ipv6/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Windows resource editors</title>
		<link>http://angelsofsecurity.com/blog/2009/02/18/windows-resource-editors/</link>
		<comments>http://angelsofsecurity.com/blog/2009/02/18/windows-resource-editors/#comments</comments>
		<pubDate>Wed, 18 Feb 2009 15:05:28 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[software]]></category>
		<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[resource editor]]></category>
		<category><![CDATA[Resource Hacker]]></category>
		<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://angelsofsecurity.com/blog/2009/02/18/windows-resource-editors/</guid>
		<description><![CDATA[I recently borrowed a copy of Hacking Windows XP from a friend. (I was under the impression that it would be about, well, hacking). It&#8217;s really all about customizations that you can do to your system, through changes to the system files and registry. One useful thing it did have was a link to a [...]]]></description>
			<content:encoded><![CDATA[<p>I recently borrowed a copy of <a href="http://www.amazon.com/Hacking-Windows-ExtremeTech-Steve-Sinchak/dp/0764569295">Hacking Windows XP</a> from a friend. (I was under the impression that it would be about, well, hacking). It&#8217;s really all about customizations that you can do to your system, through changes to the system files and registry. One useful thing it did have was a link to a very good resource editor called <a href="http://angusj.com/resourcehacker/">Resource Hacker</a>. It&#8217;s been years since I&#8217;ve used a Windows resource editor, and I&#8217;m starting to remember how fun (and utterly time consuming) it can be to mess around with the look and feel of your Windows apps and OS. In short, Resource Hacker lets you open up an executable or library file (exe, dll, ocx, scr, or cpl), and see that various resources within it &#8211; things like text string and icons &#8211; and lets you change them. Say you don&#8217;t like an error message, just find that text string and change it. Don&#8217;t like the way an app looks? Just change the icons. Don&#8217;t like the fact that the start button says start? Change it. (It&#8217;s just a text string after all). I know someone will point out that a hex editor can do many of the same things, however a resource editor organizes the data for you making it easier to find that string you want to change (or just browse), and it should (in theory at least) keep you away from the executable code which could break the app. It also let&#8217;s you see and edit graphics. If you ever want to find a fun way to kill a lazy Sunday afternoon, I highly recommend it.</p>
]]></content:encoded>
			<wfw:commentRss>http://angelsofsecurity.com/blog/2009/02/18/windows-resource-editors/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MS09-002 reverse engineered</title>
		<link>http://angelsofsecurity.com/blog/2009/02/17/ms09-002-reverse-engineered/</link>
		<comments>http://angelsofsecurity.com/blog/2009/02/17/ms09-002-reverse-engineered/#comments</comments>
		<pubDate>Tue, 17 Feb 2009 20:42:34 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[news]]></category>
		<category><![CDATA[disclosure]]></category>
		<category><![CDATA[IE7]]></category>
		<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[patch]]></category>

		<guid isPermaLink="false">http://angelsofsecurity.com/blog/2009/02/17/ms09-002-reverse-engineered/</guid>
		<description><![CDATA[ISC is reporting that they&#8217;re seeing exploits of MS09-002 in the wild. MS09-002 is an exploit which allows for remote code execution on IE7. The vulnerability was first reported to MS in October of 2007 by the Zero Day Initiative. Microsoft issued the patch a week ago. Given this, ISC is also claiming that it [...]]]></description>
			<content:encoded><![CDATA[<p>ISC is <a href="http://isc.sans.org/diary.html?storyid=5884">reporting</a> that they&#8217;re seeing exploits of <a href="http://www.microsoft.com/technet/security/bulletin/MS09-002.mspx">MS09-002</a> in the wild. MS09-002 is an exploit which allows for remote code execution on IE7. The vulnerability was first <a href="http://www.zerodayinitiative.com/advisories/ZDI-09-012/">reported to MS</a> in October of 2007 by the Zero Day Initiative. Microsoft issued the patch a week ago. Given this, ISC is also claiming that it is likely that the patch was reverse engineered to find the vulnerability, and I would have to agree. I&#8217;m sure the anti-disclosure crowd will be using this one as proof positive for their position in the future.</p>
]]></content:encoded>
			<wfw:commentRss>http://angelsofsecurity.com/blog/2009/02/17/ms09-002-reverse-engineered/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>bountys for virus writers</title>
		<link>http://angelsofsecurity.com/blog/2009/02/13/bountys-for-virus-writers/</link>
		<comments>http://angelsofsecurity.com/blog/2009/02/13/bountys-for-virus-writers/#comments</comments>
		<pubDate>Fri, 13 Feb 2009 19:23:35 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[news]]></category>
		<category><![CDATA[bounty]]></category>
		<category><![CDATA[crime]]></category>
		<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[virus]]></category>
		<category><![CDATA[worm]]></category>

		<guid isPermaLink="false">http://angelsofsecurity.com/blog/2009/02/13/bountys-for-virus-writers/</guid>
		<description><![CDATA[The Conficker worm author is the latest to latest to have a bounty placed on his/her head. While I&#8217;m not inherently opposed to rewarding people who turn in criminals (it certainly has been standard practice in the non-cyber world for centuries). However, I think that in this case the organization offering the bounty is simply [...]]]></description>
			<content:encoded><![CDATA[<p>The Conficker worm author is the <a href="http://www.securityfocus.com/news/11546?ref=rss">latest to latest to have a bounty</a> placed on his/her head. While I&#8217;m not inherently opposed to rewarding people who turn in criminals (it certainly has been standard practice in the non-cyber world for centuries). However, I think that in this case the <a href="http://www.microsoft.com/en/us/default.aspx">organization offering the bounty</a> is simply trying to look &#8220;tough on crime&#8221; after suffering for decades due to their lax security posture.</p>
<p><strong>update</strong> On a related topic, when doing some background research on conficker, I stumbled across the following headline:<br />
<center><a href="http://www.nbr.co.nz/article/french-navy-surrenders-conficker-49733">French navy surrenders to Conficker</a></center> The jokes just sort of write themselves&#8230;.</p>
]]></content:encoded>
			<wfw:commentRss>http://angelsofsecurity.com/blog/2009/02/13/bountys-for-virus-writers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Format string attacks in Windows and sort.exe</title>
		<link>http://angelsofsecurity.com/blog/2009/01/26/format-string-attacks-in-windows-and-sortexe/</link>
		<comments>http://angelsofsecurity.com/blog/2009/01/26/format-string-attacks-in-windows-and-sortexe/#comments</comments>
		<pubDate>Mon, 26 Jan 2009 15:39:46 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[application security]]></category>
		<category><![CDATA[format string attacks]]></category>
		<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[sort.exe]]></category>
		<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://angelsofsecurity.com/blog/2009/01/26/format-string-attacks-in-windows-and-sortexe/</guid>
		<description><![CDATA[Well that was a long and unexpected blogging break. It started because I wanted to write a long and detailed post about the last BGP exploit when I realized how little most security people knew about BGP. Unfortunately I never had time, a bunch of other things demanded my attention, (like real life), and then [...]]]></description>
			<content:encoded><![CDATA[<p>Well that was a long and unexpected blogging break. It started because I wanted to write a long and detailed post about the last BGP exploit when I realized how little most security people knew about BGP. Unfortunately I never had time, a bunch of other things demanded my attention, (like real life), and then once I got out of the habit of blogging, it was too easy to just ignore it. I&#8217;m back though, and I&#8217;ll try to blog regularly, albeit perhaps at a slower rate if real life persists in being as time consuming as its been lately.</p>
<p>Since this blog is coming back from a long hiatus, I think perhaps it&#8217;s appropriate to do so by bringing back an old vulnerability from a long hiatus as well. <a href="http://en.wikipedia.org/wiki/Format_string_vulnerabilities">Format String Vulnerabilities</a> have been around since around 1999. The short explanation is that when a C program doesn&#8217;t use format specifiers (you know, all those %s things you learned about way back when), but rather just prints a buffer directly, an attacker could put in format specifiers (like %x and %n). %x will just print the next hex number on the stack, so an attacker can view the stack. %n is more insidious &#8211; it is used to count the number of characters printed so far and copy that number into an arbitrary memory array. An attacker can use this to overwrite a given memory location (like, say, a return pointer) and execute arbitrary code.</p>
<p>In August of 2004 it was revealed that Windows&#8217; <a href="http://marc.info/?l=vuln-dev&#038;m=109871994406659&#038;w=2">sort.exe had a format string vulnerability</a>. Like most people, I assumed that since the fix for this is trivial (just use a format specifier instead of printing the buffer directly), Microsoft would have fixed it in the next patch release or service pack. Lo and behold, they haven&#8217;t. This is a copy and paste from the command shell of my Windows XP machine.</p>
<blockquote><p> Microsoft Windows XP [Version 5.1.2600]<br />
(C) Copyright 1985-2001 Microsoft Corp.</p>
<p>C:\&gt;ver</p>
<p>Microsoft Windows XP [Version 5.1.2600]</p>
<p>C:\&gt;sort %x<br />
7c812f39The system cannot find the file specified.</p>
<p>C:\&gt;sort %x%x<br />
7c812f390The system cannot find the file specified.</p>
<p>C:\&gt;sort %x%x%x<br />
7c812f3900The system cannot find the file specified.</p>
<p>C:\&gt;sort %x%x%x%x<br />
7c812f390078257825The system cannot find the file specified.</p>
<p>C:\&gt;sort %x%x%x%x%x<br />
7c812f39007825782578257825The system cannot find the file specified.</p>
<p>C:\&gt;sort %x%n</p>
<p>(sort.exe crashes as I&#8217;ve tried to write data to some random place in memory)</p>
<p>Everyone knows that Microsoft has a reputation for not fixing vulnerabilities unless forced to, but this is bad even by their standards. 4+ years and they haven&#8217;t fixed a know format string vulnerability.</p>
]]></content:encoded>
			<wfw:commentRss>http://angelsofsecurity.com/blog/2009/01/26/format-string-attacks-in-windows-and-sortexe/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

