<?xml version="1.0" encoding="utf-8" ?>

<rss version="2.0" 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:admin="http://webns.net/mvcb/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
   xmlns:wfw="http://wellformedweb.org/CommentAPI/"
   xmlns:content="http://purl.org/rss/1.0/modules/content/"
   >
<channel>
    <title>Niels Provos - Security</title>
    <link>http://www.provos.org/</link>
    <description>systrace, spybye and other things.</description>
    <dc:language>en</dc:language>
    <generator>Serendipity 1.3.1 - http://www.s9y.org/</generator>
    
    

<item>
    <title>Anatomy of a PDF Exploit</title>
    <link>http://www.provos.org/index.php?/archives/85-Anatomy-of-a-PDF-Exploit.html</link>
            <category>Hacking</category>
            <category>Malware</category>
            <category>Security</category>
    
    <comments>http://www.provos.org/index.php?/archives/85-Anatomy-of-a-PDF-Exploit.html#comments</comments>
    <wfw:comment>http://www.provos.org/wfwcomment.php?cid=85</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.provos.org/rss.php?version=2.0&amp;type=comments&amp;cid=85</wfw:commentRss>
    

    <author>nospam@example.com (Niels Provos)</author>
    <content:encoded>
    PDF has become the de-facto standard for formatting print documents.  Over the years, it has evolved into a &lt;a href=&quot;http://www.adobe.com/devnet/pdf/pdf_reference.html&quot;&gt;feature rich and very complex system&lt;/a&gt;.  PDF supports embedded Javascript that can be used for form validation and contains support for different image formats and 3D models, etc.  As a result, PDF implementations have numerous vulnerabilities that can be exploit by adversaries to gain control over a user’s computer.   Here are a number of CVEs that are currently being exploited in the wild: &lt;a href=&quot;http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-5659&quot;&gt;CVE-2007-5659&lt;/a&gt;, &lt;a href=&quot;http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-2992&quot;&gt;CVE-2008-2992&lt;/a&gt;, &lt;a href=&quot;http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0927&quot;&gt;CVE-2009-0927&lt;/a&gt;, &lt;a href=&quot;http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-2994&quot;&gt;CVE-2009-2994&lt;/a&gt;, &lt;a href=&quot;http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-4324&quot;&gt;CVE-2009-4324&lt;/a&gt;, &lt;a href=&quot;http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-0188&quot;&gt;CVE-2010-0188&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
In this blog post, we are going to look at current exploitation of CVE-2010-0188: An integer overflow in the parsing of the dot range option in TIFF files.   The vulnerability was publicly &lt;a href=&quot;http://www.adobe.com/support/security/bulletins/apsb10-07.html&quot;&gt;announced in February 2010&lt;/a&gt;.  Examples of &lt;a href=&quot;http://www.exploit-db.com/exploits/11787/&quot;&gt;exploit code&lt;/a&gt; are readily available on the Internet and a very good explanation of how the exploit works has been provided by &lt;a href=&quot;http://blog.fortinet.com/cve-2010-0188-exploit-in-the-wild/&quot;&gt;Fortinet&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
The exploit described by Fortinet utilizes an AcroForm described in XML.  The XML contains an image field with an embedded TIFF image that triggers the vulnerability.&lt;br /&gt;
&lt;br /&gt;
&lt;!-- s9ymdb:12 --&gt;&lt;img class=&quot;serendipity_image_left&quot; width=&quot;691&quot; height=&quot;209&quot; style=&quot;border: 0px; padding-left: 5px; padding-right: 5px; padding-bottom: 10px;&quot; src=&quot;http://www.provos.org/uploads/image2.png&quot; alt=&quot;&quot; /&gt; &lt;br /&gt;&lt;a href=&quot;http://www.provos.org/index.php?/archives/85-Anatomy-of-a-PDF-Exploit.html#extended&quot;&gt;Continue reading &quot;Anatomy of a PDF Exploit&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Thu, 19 Aug 2010 17:10:08 -0700</pubDate>
    <guid isPermaLink="false">http://www.provos.org/index.php?/archives/85-guid.html</guid>
    <category>exploit</category>
<category>malware</category>
<category>pdf</category>

</item>
<item>
    <title>LEET '10 Call for Papers</title>
    <link>http://www.provos.org/index.php?/archives/74-LEET-10-Call-for-Papers.html</link>
            <category>Malware</category>
            <category>News</category>
            <category>Security</category>
    
    <comments>http://www.provos.org/index.php?/archives/74-LEET-10-Call-for-Papers.html#comments</comments>
    <wfw:comment>http://www.provos.org/wfwcomment.php?cid=74</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.provos.org/rss.php?version=2.0&amp;type=comments&amp;cid=74</wfw:commentRss>
    

    <author>nospam@example.com (Niels Provos)</author>
    <content:encoded>
    The call for papers for the &lt;strong&gt;3rd USENIX Workshop on Large-Scale Exploits and Emergent Threats&lt;/strong&gt; (LEET &#039;10) Botnets, Spyware, Worms, and More just went out.   It will be held on &lt;strong&gt;April 27, 2010&lt;/strong&gt; in San Jose, CA.&lt;br /&gt;
&lt;br /&gt;
&lt;a href=&quot;http://www.usenix.org/event/leet10/cfp/&quot;&gt;LEET &#039;10&lt;/a&gt; will be co-located with the 7th USENIX Symposium on Networked Systems Design and Implementation (NSDI &#039;10), which will take place April 28–30, 2010.&lt;br /&gt;
&lt;br /&gt;
&lt;strong&gt;Important Dates&lt;/strong&gt;&lt;br /&gt;
&lt;ul&gt;&lt;li&gt;Submissions due: Thursday, February 25, 2010, 11:59 p.m. PST&lt;/li&gt;&lt;li&gt;Notification of acceptance: Wednesday, March 24, 2010&lt;/li&gt;&lt;li&gt;Final papers due: Monday, April 5, 2010&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;
&lt;strong&gt;Workshop Organizers&lt;/strong&gt;&lt;br /&gt;
&lt;em&gt;Program Chair&lt;/em&gt;&lt;ul&gt;&lt;li&gt;Michael Bailey, University of Michigan&lt;/li&gt;&lt;/ul&gt;&lt;em&gt;Program Committee&lt;/em&gt;&lt;ul&gt;&lt;li&gt;Dan Boneh, Stanford University&lt;/li&gt;&lt;li&gt;Nick Feamster, Georgia Institute of Technology&lt;/li&gt;&lt;li&gt;Jaeyeon Jung, Intel Labs, Seattle&lt;/li&gt;&lt;li&gt;Christian Kreibich, International Computer Science Institute&lt;/li&gt;&lt;li&gt;Patrick McDaniel, Pennsylvania State University&lt;/li&gt;&lt;li&gt;Fabian Monrose, University of North Carolina, Chapel Hill&lt;/li&gt;&lt;li&gt;Jose Nazario, Arbor Networks, Inc.&lt;/li&gt;&lt;li&gt;Stefan Savage, University of California, San Diego&lt;/li&gt;&lt;li&gt;Matt Williamson, AVG Technologies&lt;/li&gt;&lt;li&gt;Yinglian Xie, Microsoft Research&lt;/li&gt;&lt;li&gt;Vinod Yegneswaran, SRI International&lt;/li&gt;&lt;br /&gt;
&lt;/ul&gt;Go submit your work! 
    </content:encoded>

    <pubDate>Sat, 29 Aug 2009 12:35:46 -0700</pubDate>
    <guid isPermaLink="false">http://www.provos.org/index.php?/archives/74-guid.html</guid>
    <category>cfp</category>
<category>malware</category>
<category>research</category>
<category>security</category>

</item>
<item>
    <title>DirectShow Vulnerability Exploited Everywhere</title>
    <link>http://www.provos.org/index.php?/archives/70-DirectShow-Vulnerability-Exploited-Everywhere.html</link>
            <category>Malware</category>
            <category>Security</category>
            <category>SpyBye</category>
    
    <comments>http://www.provos.org/index.php?/archives/70-DirectShow-Vulnerability-Exploited-Everywhere.html#comments</comments>
    <wfw:comment>http://www.provos.org/wfwcomment.php?cid=70</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.provos.org/rss.php?version=2.0&amp;type=comments&amp;cid=70</wfw:commentRss>
    

    <author>nospam@example.com (Niels Provos)</author>
    <content:encoded>
    The &lt;a href=&quot;http://secunia.com/advisories/35683/&quot;&gt;DirectShow&lt;/a&gt; &lt;a href=&quot;http://www.symantec.com/connect/blogs/directshow-exploit-wild&quot;&gt;vulnerabilities&lt;/a&gt; are being exploited all over the place now.  Unfortunately, the &lt;a href=&quot;http://www.computerworld.com/s/article/9135210/Hackers_exploit_second_DirectShow_zero_day_using_thousands_of_hijacked_sites&quot;&gt;second vulnerability&lt;/a&gt; in DirectShow is still unpatched and exploit sites seem to be jumping on this.  There is even some evidence that it&#039;s possible to &lt;a href=&quot;http://www.viruslist.com/en/weblog?weblogid=208187760&quot;&gt;successfully exploit&lt;/a&gt; the vulnerability without even using JavaScript.   New &lt;a href=&quot;http://isc.sans.org/diary.html?storyid=6739&quot;&gt;exploit domains&lt;/a&gt; are popping after &lt;a href=&quot;http://google.com/safebrowsing/diagnostic?site=ch.ma/&quot;&gt;every day&lt;/a&gt;.  DirectShow now seems to be what Flash and PDF were earlier in the year. 
    </content:encoded>

    <pubDate>Sat, 11 Jul 2009 09:38:16 -0700</pubDate>
    <guid isPermaLink="false">http://www.provos.org/index.php?/archives/70-guid.html</guid>
    <category>exploit</category>
<category>malware</category>
<category>security</category>

</item>
<item>
    <title>Cybercrime 2.0: When the Cloud Turns Dark</title>
    <link>http://www.provos.org/index.php?/archives/66-Cybercrime-2.0-When-the-Cloud-Turns-Dark.html</link>
            <category>Malware</category>
            <category>Security</category>
            <category>SpyBye</category>
    
    <comments>http://www.provos.org/index.php?/archives/66-Cybercrime-2.0-When-the-Cloud-Turns-Dark.html#comments</comments>
    <wfw:comment>http://www.provos.org/wfwcomment.php?cid=66</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.provos.org/rss.php?version=2.0&amp;type=comments&amp;cid=66</wfw:commentRss>
    

    <author>nospam@example.com (Niels Provos)</author>
    <content:encoded>
    We recently published an article on &lt;a href=&quot;http://queue.acm.org/detail.cfm?id=1517412&quot;&gt;web-based malware&lt;/a&gt; in ACM&#039;s Queue Magazine.  It provides a short overview of some of the challenges with detecting malicious web sites such as social engineering and examples of techniques for compromising web sites, e.g. htaccess redirection on Apache, etc.  This is the article on which my recent ISSNet talk was based. 
    </content:encoded>

    <pubDate>Wed, 01 Jul 2009 08:19:59 -0700</pubDate>
    <guid isPermaLink="false">http://www.provos.org/index.php?/archives/66-guid.html</guid>
    <category>exploit</category>
<category>malware</category>
<category>security</category>

</item>
<item>
    <title>Top 10 Malware Sites</title>
    <link>http://www.provos.org/index.php?/archives/63-Top-10-Malware-Sites.html</link>
            <category>Malware</category>
            <category>News</category>
            <category>Security</category>
            <category>SpyBye</category>
    
    <comments>http://www.provos.org/index.php?/archives/63-Top-10-Malware-Sites.html#comments</comments>
    <wfw:comment>http://www.provos.org/wfwcomment.php?cid=63</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.provos.org/rss.php?version=2.0&amp;type=comments&amp;cid=63</wfw:commentRss>
    

    <author>nospam@example.com (Niels Provos)</author>
    <content:encoded>
    A list of the &lt;a href=&quot;http://googleonlinesecurity.blogspot.com/2009/06/top-10-malware-sites.html&quot;&gt;top-10 malware&lt;/a&gt; sites found by Google&#039;s infrastructure over the last two months is available at the &lt;a href=&quot;http://googleonlinesecurity.blogspot.com/&quot;&gt;Google Online Security Blog&lt;/a&gt;.  Gumblar and Martuz are among them as well as &lt;a href=&quot;http://google.com/safebrowsing/diagnostic?site=googleanalytlcs.net&quot;&gt;googleanalytlcs.net&lt;/a&gt;.   There certainly have been lots of compromised web servers recently. 
    </content:encoded>

    <pubDate>Sat, 06 Jun 2009 10:03:02 -0700</pubDate>
    <guid isPermaLink="false">http://www.provos.org/index.php?/archives/63-guid.html</guid>
    <category>malware</category>

</item>
<item>
    <title>LEET'09: Large Scale Exploits and Emergent Threats</title>
    <link>http://www.provos.org/index.php?/archives/62-LEET09-Large-Scale-Exploits-and-Emergent-Threats.html</link>
            <category>Malware</category>
            <category>News</category>
            <category>Security</category>
    
    <comments>http://www.provos.org/index.php?/archives/62-LEET09-Large-Scale-Exploits-and-Emergent-Threats.html#comments</comments>
    <wfw:comment>http://www.provos.org/wfwcomment.php?cid=62</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.provos.org/rss.php?version=2.0&amp;type=comments&amp;cid=62</wfw:commentRss>
    

    <author>nospam@example.com (Niels Provos)</author>
    <content:encoded>
    The 2nd USENIX LEET workshop is going to take place on April 21st in Boston next week.   The &lt;a href=&quot; http://www.usenix.org/events/leet09/tech/tech.html&quot;&gt;workshop program&lt;/a&gt; looks really interesting.  There are a number of really interesting talks; here are just a few:&lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;&lt;li&gt;Spamcraft: An Inside Look At Spam Campaign Orchestration&lt;/li&gt;&lt;li&gt;A Foray into Conficker&#039;s Logic and Rendezvous Points&lt;/li&gt;&lt;li&gt;A View on Current Malware Behaviors&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;
&lt;br /&gt;
Last year&#039;s workshop was a blast and I expect that next week is going to be lots of fun, too.   It is still possible to &lt;a href=&quot;http://www.usenix.org/events/leet09/registration/&quot;&gt;register on-site&lt;/a&gt; for the workshop. 
    </content:encoded>

    <pubDate>Tue, 14 Apr 2009 17:25:08 -0700</pubDate>
    <guid isPermaLink="false">http://www.provos.org/index.php?/archives/62-guid.html</guid>
    <category>security</category>
<category>usenix</category>

</item>
<item>
    <title>LEET '09 Call for Papers</title>
    <link>http://www.provos.org/index.php?/archives/52-LEET-09-Call-for-Papers.html</link>
            <category>News</category>
            <category>Security</category>
            <category>Systrace</category>
    
    <comments>http://www.provos.org/index.php?/archives/52-LEET-09-Call-for-Papers.html#comments</comments>
    <wfw:comment>http://www.provos.org/wfwcomment.php?cid=52</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.provos.org/rss.php?version=2.0&amp;type=comments&amp;cid=52</wfw:commentRss>
    

    <author>nospam@example.com (Niels Provos)</author>
    <content:encoded>
    The &lt;a href=&quot;http://www.usenix.org/event/leet09/cfp/&quot;&gt;CfP&lt;/a&gt; for the 2nd USENIX Workshop on Large-Scale Exploits and Emergent Threats (LEET &#039;09): Botnets, Spyware, Worms, and More is up at:&lt;br /&gt;
&lt;br /&gt;
&lt;dl&gt;&lt;dd&gt;&lt;a href=&quot;http://www.usenix.org/event/leet09/cfp/&quot;&gt;http://www.usenix.org/event/leet09/cfp/&lt;/a&gt;.&lt;/dd&gt;&lt;/dl&gt;&lt;br /&gt;
LEET &#039;09 will be held on April 21, 2009 in Boston, MA immediately before the 6th USENIX Symposium on Networked Systems Design and Implementation (NSDI &#039;09), which will take place April 22–24, 2009. &lt;br /&gt;
&lt;br /&gt;
&lt;strong&gt;Important Dates&lt;/strong&gt;&lt;br /&gt;
&lt;ul&gt;&lt;li&gt;Submissions due: January 16, 2009, 11:59 p.m. EST&lt;/li&gt;&lt;li&gt;Notification of acceptance: March 2, 2009&lt;/li&gt;&lt;li&gt;Electronic files due: March 30, 2009&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;
This will be the second edition of LEET, which had evolved from the combination of two other successful workshops, the ACM Workshop on Recurring Malcode (WORM) and the USENIX Workshop on Hot Topics in Understanding Botnets (HotBots). These two workshops have each dealt with aspects of this problem. However, while papers relating to both worms and botnets are explicitly solicited, LEET has a broader charter than its predecessors. We encourage submissions of papers that focus on any aspect of the underlying mechanisms used to compromise and control hosts, the large-scale &quot;applications&quot; being perpetrated upon this framework, or the social and economic networks driving these threats. 
    </content:encoded>

    <pubDate>Wed, 12 Nov 2008 18:48:12 -0800</pubDate>
    <guid isPermaLink="false">http://www.provos.org/index.php?/archives/52-guid.html</guid>
    <category>cfp</category>
<category>research</category>
<category>security</category>
<category>usenix</category>

</item>
<item>
    <title>DNS And Responsible Disclosure</title>
    <link>http://www.provos.org/index.php?/archives/44-DNS-And-Responsible-Disclosure.html</link>
            <category>Hacking</category>
            <category>Security</category>
    
    <comments>http://www.provos.org/index.php?/archives/44-DNS-And-Responsible-Disclosure.html#comments</comments>
    <wfw:comment>http://www.provos.org/wfwcomment.php?cid=44</wfw:comment>

    <slash:comments>3</slash:comments>
    <wfw:commentRss>http://www.provos.org/rss.php?version=2.0&amp;type=comments&amp;cid=44</wfw:commentRss>
    

    <author>nospam@example.com (Niels Provos)</author>
    <content:encoded>
    As everyone was upgrading their DNS infrastructure to be ready for August 7th, some security reseachers independently discovered the DNS flaw and disclosed it.  For those of us, who were either informed or had figured out the problem ourselves, it is surprising to find irresponsible and grossly negligent disclosure from respected members of our community.   There was a reason that Kaminsky did not disclose the flaw publicly when he found it.   The DNS infrastructure needed to be upgraded and repaired.&lt;br /&gt;
&lt;br /&gt;
Well, the time has run out.  A current study by David Dagon and myself puts the number of open recursive resolvers using static source ports at about &lt;strong&gt;78%&lt;/strong&gt;.   That is a lot of servers that need to be patched.  Two more weeks till August 7th could have helped to fix many of them.  Unfortunately, we will not find out now. 
    </content:encoded>

    <pubDate>Tue, 22 Jul 2008 09:15:00 -0700</pubDate>
    <guid isPermaLink="false">http://www.provos.org/index.php?/archives/44-guid.html</guid>
    <category>dns</category>
<category>security</category>

</item>
<item>
    <title>DNS Testing Image</title>
    <link>http://www.provos.org/index.php?/archives/43-DNS-Testing-Image.html</link>
            <category>Hacking</category>
            <category>Security</category>
    
    <comments>http://www.provos.org/index.php?/archives/43-DNS-Testing-Image.html#comments</comments>
    <wfw:comment>http://www.provos.org/wfwcomment.php?cid=43</wfw:comment>

    <slash:comments>2</slash:comments>
    <wfw:commentRss>http://www.provos.org/rss.php?version=2.0&amp;type=comments&amp;cid=43</wfw:commentRss>
    

    <author>nospam@example.com (Niels Provos)</author>
    <content:encoded>
    As we are all trying to patch and upgrade our resolvers and NAT devices, I created a small image tag that automatically assesses the randomess of a visitor&#039;s resolver:&lt;br /&gt;
&lt;br /&gt;
&lt;center&gt;&lt;a href=&quot;http://www.provos.org/index.php?/archives/42-DNS-and-Randomness.html&quot;&gt;&lt;img src=&quot;http://porttest.honeyd.org/-s-_dns.png&quot; border=0&gt;&lt;/a&gt;&lt;/center&gt;This is still in reference to the CERT Advisory on &lt;a href=&quot;http://www.kb.cert.org/vuls/id/800113&quot;&gt;Multiple DNS implementations vulnerable to cache poisoning&lt;/a&gt;.  You can place the image tag on your web page to test your visitors:&lt;br /&gt;
&lt;blockquote&gt;&amp;lt;center&amp;gt;&amp;lt;a href=&quot;http://www.provos.org/index.php?/archives/42-DNS-and-Randomness.html&quot;&amp;gt;&amp;lt;img src=&quot;http://porttest.honeyd.org/-s-_dns.png&quot; border=0&amp;gt;&amp;lt;/a&amp;gt;&amp;lt;/center&amp;gt; &lt;/blockquote&gt;&lt;br /&gt;
&lt;br /&gt;
The &lt;em&gt;a href&lt;/em&gt; link can of course point to a more helpful web page and the image itself can also be changed according to need.&lt;br /&gt;
&lt;br /&gt;
If you want to show this on your pages with different images, just let me know.&lt;br /&gt;
&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Tue, 15 Jul 2008 19:11:50 -0700</pubDate>
    <guid isPermaLink="false">http://www.provos.org/index.php?/archives/43-guid.html</guid>
    <category>dns</category>
<category>security</category>

</item>

</channel>
</rss>