<?xml version="1.0"?>
<rss version="2.0">
    <channel>
        <title>OpenRCE: Blog</title>
        <link>http://www.openrce.org/rss/feeds/blog</link>
        <description>OpenRCE: The Open Reverse Code Engineering Community</description>
                <item>
            <title>Windows &amp;quot;DbgHelp.dll&amp;quot; Export name stack overflow vulnerability</title>
                            <pubDate>Wed, 10 Nov 2010 05:35:05 -0600</pubDate>
                                        <link>https://www.openrce.org/blog/view/1622/Windows_&quot;DbgHelp.dll&quot;_Export_name_stack_overflow_vulnerability</link>
                                        <author>dragula &lt;email-suppressed@example.com&gt;</author>
                                                    <description>Malwares are exploiting this vulnerability to protect their code from debugging...&lt;br /&gt;
This link has pretty good information about this vulnerability.&lt;br /&gt;
&lt;br /&gt;
http://foolishpages.blogspot.com/2010/11/windows-dbghelpdll-export-name-stack.html</description>
                    </item>
                <item>
            <title>Reversing compiler infector Induc.a</title>
                            <pubDate>Fri, 29 Jan 2010 10:43:35 -0600</pubDate>
                                        <link>https://www.openrce.org/blog/view/1545/Reversing_compiler_infector_Induc.a</link>
                                        <author>dragula &lt;email-suppressed@example.com&gt;</author>
                                                    <description>I have seen full analysis document of compiler infector Induc at :&lt;br /&gt;
&lt;br /&gt;
http://foolishpages.blogspot.com/2010/01/tracing-infecting-code-in.html</description>
                    </item>
            </channel>
</rss>
