<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
    <channel>
        <title>Vulnerability Analysis Blog</title>
        <link>https://www.cert.org/blogs/vuls/</link>
        <description></description>
        <language>en</language>
        <copyright>Copyright 2010</copyright>
        <lastBuildDate>Wed, 26 May 2010 13:56:27 -0500</lastBuildDate>
        <generator>http://www.sixapart.com/movabletype/</generator>
        <docs>http://www.rssboard.org/rss-specification</docs>
        
        <item>
            <title>CERT Basic Fuzzing Framework</title>
            <description><![CDATA[<p>Hi folks. I've been involved in a fuzzing effort at CERT. One of the ways that I've been able to discover vulnerabilities is through &quot;dumb&quot;&nbsp;or mutational <a href="http://en.wikipedia.org/wiki/Fuzz_testing">fuzzing</a>. We have developed a framework for performing automated <a href="http://msdn.microsoft.com/en-us/library/cc162782.aspx#Fuzzing_topic4">dumb fuzzing</a>. Today we are releasing a simplified version of automated dumb fuzzing, called the Basic Fuzzing Framework (BFF).</p>]]></description>
            <link>https://www.cert.org/blogs/vuls/2010/05/cert_basic_fuzzing_framework.html</link>
            <guid>https://www.cert.org/blogs/vuls/2010/05/cert_basic_fuzzing_framework.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Discovery</category>
            
            
            <pubDate>Wed, 26 May 2010 13:56:27 -0500</pubDate>
        </item>
        
        <item>
            <title>Top-10 Top Level and Second Level Domains found in Malicious Software</title>
            <description><![CDATA[<p>Hello folks.&nbsp; This post comes to you courtesy of Ed Stoner and Aaron Shelmire from the <a href="http://www.cert.org/netsa/">Network  Situational Awareness</a> group at CERT.&nbsp; They write:</p> <p>Recently there have been some <a href="http://blog.damballa.com/?p=575">statistics  published</a> on botnet Command &amp; Control (C2) channels. These  statistics claim that 94.58% of botnet C2 channels are under the .com  top level domain (TLD). While it's impossible to accurately comment on  those statistics without knowing the methodology used to arrive at them,   we at CERT have been doing research concerning malicious domain names  that arrives at a different result.</p>]]></description>
            <link>https://www.cert.org/blogs/vuls/2010/03/top-10_top_level_and_second_le.html</link>
            <guid>https://www.cert.org/blogs/vuls/2010/03/top-10_top_level_and_second_le.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Analysis</category>
            
                <category domain="http://www.sixapart.com/ns/types#category">Web</category>
            
            
            <pubDate>Fri, 05 Mar 2010 14:10:32 -0500</pubDate>
        </item>
        
        <item>
            <title>Plain Text Email in Outlook Express</title>
            <description><![CDATA[<p>Reading email messages in plain text seems like a reasonable thing to do to improve the security of your email client. Plain text takes less processing than HTML, which should help minimize your attack surface, right? As it turns out, Outlook Express (and its derivatives) is doing more than you think when it is configured with the &quot;Read all messages in plain text&quot;&nbsp;option enabled.</p>]]></description>
            <link>https://www.cert.org/blogs/vuls/2009/11/plain_text_email_in_outlook_ex.html</link>
            <guid>https://www.cert.org/blogs/vuls/2009/11/plain_text_email_in_outlook_ex.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Analysis</category>
            
            
            <pubDate>Fri, 13 Nov 2009 09:23:00 -0500</pubDate>
        </item>
        
        <item>
            <title>Managing IPv6 - Part 2</title>
            <description><![CDATA[<p>Past entries have addressed both securing and disabling IPv6. This entry describes ways that administrators can secure their networks and generate test cases to test those settings.</p>]]></description>
            <link>https://www.cert.org/blogs/vuls/2009/10/managing_ipv6_-_part_2.html</link>
            <guid>https://www.cert.org/blogs/vuls/2009/10/managing_ipv6_-_part_2.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Analysis</category>
            
            
            <pubDate>Tue, 06 Oct 2009 15:44:00 -0500</pubDate>
        </item>
        
        <item>
            <title>Managing IPv6 - Part 1</title>
            <description><![CDATA[<p>This entry is the first in a series about securely configuring the <a href="http://en.wikipedia.org/w/index.php?title=IPv6&amp;oldid=306038060">IPv6</a> protocol on selected operating systems. Although this entry focuses on how to disable IPv6, we are not recommending that everyone immediately disable IPv6. However, if critical parts of your infrastructure (firewall, IDS, etc.) do not yet fully support the IPv6 protocol, consider disabling IPv6 until those components can be upgraded.</p>]]></description>
            <link>https://www.cert.org/blogs/vuls/2009/08/managing_ipv6_part_i.html</link>
            <guid>https://www.cert.org/blogs/vuls/2009/08/managing_ipv6_part_i.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Analysis</category>
            
            
            <pubDate>Wed, 19 Aug 2009 10:07:00 -0500</pubDate>
        </item>
        
        <item>
            <title>Internet Explorer Kill-Bits</title>
            <description><![CDATA[<p>The Kill-Bit (or &quot;killbit&quot;) is a Microsoft Windows registry value that prevents an ActiveX control from being used by Internet Explorer. More information is available in Microsoft KB article <a href="http://support.microsoft.com/kb/240797">240797</a>. If a vulnerability is discovered in an ActiveX control or COM object, a common mitigation is to set the killbit for the control, which will cause Internet Explorer to block use of the control. Or will it?</p>]]></description>
            <link>https://www.cert.org/blogs/vuls/2009/07/internet_explorer_kill-bits.html</link>
            <guid>https://www.cert.org/blogs/vuls/2009/07/internet_explorer_kill-bits.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Analysis</category>
            
                <category domain="http://www.sixapart.com/ns/types#category">Discovery</category>
            
                <category domain="http://www.sixapart.com/ns/types#category">Web</category>
            
            
            <pubDate>Fri, 31 Jul 2009 15:18:00 -0500</pubDate>
        </item>
        
        <item>
            <title>Mitigating Slowloris</title>
            <description><![CDATA[<p>Slowloris is a denial-of-service (DoS) tool that targets web servers. We have some suggestions about mitigation techniques and workarounds to protect your server. However, use caution if you implement any of these suggestions because they will likely have some unintended side effects.</p>]]></description>
            <link>https://www.cert.org/blogs/vuls/2009/07/slowloris_vs_your_webserver.html</link>
            <guid>https://www.cert.org/blogs/vuls/2009/07/slowloris_vs_your_webserver.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Analysis</category>
            
            
            <pubDate>Wed, 01 Jul 2009 12:18:00 -0500</pubDate>
        </item>
        
        <item>
            <title>Vulnerabilities and Attack Surface</title>
            <description><![CDATA[<p>Two recent <a href="http://www.kb.cert.org/vuls/byid?searchview&amp;query=VU%23251793,VU%23568153">US-CERT Vulnerability Notes</a> describe similar issues in the Adobe Reader and Foxit Reader PDF viewing applications. The vulnerabilities, that both applications failed to properly handle JPEG2000 (JPX) data streams, were discovered as part of our <a href="http://www.cert.org/vuls/discovery/">Vulnerability Discovery</a> initiative. The two vulnerability notes are quite similar, except for one aspect: attack surface.</p>]]></description>
            <link>https://www.cert.org/blogs/vuls/2009/06/vulnerabilities_and_software_a.html</link>
            <guid>https://www.cert.org/blogs/vuls/2009/06/vulnerabilities_and_software_a.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Discovery</category>
            
            
            <pubDate>Thu, 25 Jun 2009 12:02:00 -0500</pubDate>
        </item>
        
        <item>
            <title>Release of Dranzer ActiveX Fuzzing Tool</title>
            <description><![CDATA[<p>Hi, it's Will. As <a href="http://www.cert.org/blogs/vuls/2008/07/activex_vulnerability_discover.html">previously mentioned</a>, we have been investigating and discovering ActiveX&nbsp;vulnerabilities over the past few years. Today we released the Dranzer tool that we have developed to test ActiveX&nbsp;controls.</p>]]></description>
            <link>https://www.cert.org/blogs/vuls/2009/04/release_of_dranzer_activex_fuz.html</link>
            <guid>https://www.cert.org/blogs/vuls/2009/04/release_of_dranzer_activex_fuz.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Discovery</category>
            
                <category domain="http://www.sixapart.com/ns/types#category">Research</category>
            
                <category domain="http://www.sixapart.com/ns/types#category">Web</category>
            
            
            <pubDate>Thu, 16 Apr 2009 11:50:26 -0500</pubDate>
        </item>
        
        <item>
            <title>Bypassing firewalls with IPv6 tunnels</title>
            <description><![CDATA[<p>Hello, it's Ryan. We've talked about IPv6 in blog <a href="http://www.cert.org/blogs/vuls/2008/09/ping_sweeping_in_ipv6.html">entries</a> and vulnerability notes before. But instead of focusing on IPv6 vulnerabilities, this blog entry will show how functional IPv6 tunneling protocols can be used to bypass IPv4-only firewalls and ACLs. If you'd like a demonstration, watch this <a href="http://www.youtube.com/watch?v=1ldPKIobPgs">video</a> that we created.</p>]]></description>
            <link>https://www.cert.org/blogs/vuls/2009/04/bypassing_firewalls_with_ipv6.html</link>
            <guid>https://www.cert.org/blogs/vuls/2009/04/bypassing_firewalls_with_ipv6.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Analysis</category>
            
            
            <pubDate>Thu, 02 Apr 2009 11:05:00 -0500</pubDate>
        </item>
        
        <item>
            <title>Conficker.C:  How many are there?</title>
            <description><![CDATA[<p>Hello, Sid Faber from the <a href="http://www.cert.org/netsa/">Network Situational Awareness</a> group at CERT. Like just about everyone else, we've been following the Conficker worm for a while and thought some updated stats on the Conficker.C variant might be useful.</p>]]></description>
            <link>https://www.cert.org/blogs/vuls/2009/03/confickerc_how_many_are_there.html</link>
            <guid>https://www.cert.org/blogs/vuls/2009/03/confickerc_how_many_are_there.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Analysis</category>
            
                <category domain="http://www.sixapart.com/ns/types#category">Research</category>
            
            
            <pubDate>Tue, 31 Mar 2009 18:10:14 -0500</pubDate>
        </item>
        
        <item>
            <title>Windows Installer Application Resiliency</title>
            <description><![CDATA[<p>Hi, it's Will again. Recently, I was investigating the effectiveness of the workarounds for the Adobe Reader <a href="http://www.kb.cert.org/vuls/id/905281">JBIG2 vulnerability</a>, and I&nbsp;encountered an unexpected situation. In certain situations, the <a href="http://msdn.microsoft.com/en-us/library/aa302344.aspx">application resiliency</a> feature of Windows Installer can actually undo some of the steps taken to mitigate a vulnerability.</p>]]></description>
            <link>https://www.cert.org/blogs/vuls/2009/03/windows_installer_application.html</link>
            <guid>https://www.cert.org/blogs/vuls/2009/03/windows_installer_application.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Analysis</category>
            
                <category domain="http://www.sixapart.com/ns/types#category">Research</category>
            
            
            <pubDate>Fri, 13 Mar 2009 13:46:00 -0500</pubDate>
        </item>
        
        <item>
            <title>Internet Explorer Vulnerability Attack Vectors</title>
            <description><![CDATA[<p>Hey, it's Will. I noticed that several blogs, including <a href="http://blog.trendmicro.com/another-exploit-targets-ie7-bug/">Trend Micro</a> and <a href="http://www.avertlabs.com/research/blog/index.php/2009/02/17/ms09-002-exploit-in-the-wild-uses-msword-lure/">McAfee</a>, have been talking about the recent attacks on the Internet Explorer 7 vulnerability that was fixed in <a href="http://www.microsoft.com/technet/security/bulletin/MS09-002.mspx">MS09-002</a>. An interesting thing about these exploits is the attack vector. The technique used in these attacks has several security impacts that may not be immediately obvious.</p>]]></description>
            <link>https://www.cert.org/blogs/vuls/2009/02/internet_explorer_vulnerabilit.html</link>
            <guid>https://www.cert.org/blogs/vuls/2009/02/internet_explorer_vulnerabilit.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Analysis</category>
            
                <category domain="http://www.sixapart.com/ns/types#category">Web</category>
            
            
            <pubDate>Thu, 19 Feb 2009 15:30:00 -0500</pubDate>
        </item>
        
        <item>
            <title>Reference Implementations for Securing Your Web Browser Guidelines</title>
            <description><![CDATA[<p>It's Will again, with the first blog entry of 2009. Our <a href="https://www.cert.org/tech_tips/securing_browser">Securing Your Web Browser</a> document describes how to make your web browser more secure, but applying all of the necessary changes can be a bit tedious. To make the process easier, we developed reference implementations of the guidelines for both Microsoft Internet Explorer and Mozilla Firefox.</p>]]></description>
            <link>https://www.cert.org/blogs/vuls/2009/01/reference_implementations_for.html</link>
            <guid>https://www.cert.org/blogs/vuls/2009/01/reference_implementations_for.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Web</category>
            
            
            <pubDate>Fri, 09 Jan 2009 11:03:00 -0500</pubDate>
        </item>
        
        <item>
            <title>Recommendations to vendors for communicating product security information</title>
            <description><![CDATA[<p>Hi, this is Chad Dougherty of the Vulnerability Analysis team. One of the important roles that our team plays is coordinating vulnerability information among a broad range of vendors. Over the years, we have gained a considerable amount of experience communicating with vendors of all shapes and sizes. Based on this experience, we can offer some guidance to vendors about communicating product security issues.</p>]]></description>
            <link>https://www.cert.org/blogs/vuls/2008/11/recommendations_to_vendors_for_communicating_product_security_information.html</link>
            <guid>https://www.cert.org/blogs/vuls/2008/11/recommendations_to_vendors_for_communicating_product_security_information.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Disclosure</category>
            
            
            <pubDate>Thu, 20 Nov 2008 16:10:00 -0500</pubDate>
        </item>
        
    </channel>
</rss>
