<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: The DNS Vuln</title>
	<atom:link href="http://www.computerdefense.org/2007/04/the-dns-vuln/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.computerdefense.org/2007/04/the-dns-vuln/</link>
	<description>Sharing my thoughts with the world.</description>
	<lastBuildDate>Wed, 16 Nov 2011 02:58:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: LonerVamp</title>
		<link>http://www.computerdefense.org/2007/04/the-dns-vuln/comment-page-1/#comment-77452</link>
		<dc:creator>LonerVamp</dc:creator>
		<pubDate>Mon, 19 Jan 2009 14:20:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.computerdefense.org/?p=308#comment-77452</guid>
		<description>There could be an insider case made as well. I know our DCs double as our internal-only DNS servers. This vuln in the DNS means our DCs could be popped internally. The only real solution (for us, I think) is to migrate DNS off the DCs. But that&#039;s not something the team wants to do, so we&#039;ll just wait for a patch. My IPS should notice this attack, thankfully.

I&#039;d be curious if this turns into a worm. I think a worm that combines mass-mail along with internet/intranet scanning could be pretty damaging.

Code Red, no. But I think the number of Windows DNS servers is underestimated. Externally, no, but internally, there&#039;s a lof of them...and they&#039;re likely all in the very soft underbelly of networks making them very juicy indeed...


Post the damned VERT solution. And yes, while I got your email, I just haven&#039;t had time or luck with that challenge. :</description>
		<content:encoded><![CDATA[<p>There could be an insider case made as well. I know our DCs double as our internal-only DNS servers. This vuln in the DNS means our DCs could be popped internally. The only real solution (for us, I think) is to migrate DNS off the DCs. But that&#039;s not something the team wants to do, so we&#039;ll just wait for a patch. My IPS should notice this attack, thankfully.</p>
<p>I&#039;d be curious if this turns into a worm. I think a worm that combines mass-mail along with internet/intranet scanning could be pretty damaging.</p>
<p>Code Red, no. But I think the number of Windows DNS servers is underestimated. Externally, no, but internally, there&#039;s a lof of them&#8230;and they&#039;re likely all in the very soft underbelly of networks making them very juicy indeed&#8230;</p>
<p>Post the damned VERT solution. And yes, while I got your email, I just haven&#039;t had time or luck with that challenge. :</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: .:Computer Defense:. &#187; RPC DNS Worm</title>
		<link>http://www.computerdefense.org/2007/04/the-dns-vuln/comment-page-1/#comment-7033</link>
		<dc:creator>.:Computer Defense:. &#187; RPC DNS Worm</dc:creator>
		<pubDate>Tue, 17 Apr 2007 14:59:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.computerdefense.org/?p=308#comment-7033</guid>
		<description>[...] Yesterday I questioned if we&#8217;d see a worm related to the RPC DNS Vuln&#8230; [...]</description>
		<content:encoded><![CDATA[<p>[...] Yesterday I questioned if we&#8217;d see a worm related to the RPC DNS Vuln&#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LonerVamp</title>
		<link>http://www.computerdefense.org/2007/04/the-dns-vuln/comment-page-1/#comment-6954</link>
		<dc:creator>LonerVamp</dc:creator>
		<pubDate>Mon, 16 Apr 2007 15:09:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.computerdefense.org/?p=308#comment-6954</guid>
		<description>There could be an insider case made as well. I know our DCs double as our internal-only DNS servers. This vuln in the DNS means our DCs could be popped internally. The only real solution (for us, I think) is to migrate DNS off the DCs. But that&#039;s not something the team wants to do, so we&#039;ll just wait for a patch. My IPS should notice this attack, thankfully.

I&#039;d be curious if this turns into a worm. I think a worm that combines mass-mail along with internet/intranet scanning could be pretty damaging.

Code Red, no. But I think the number of Windows DNS servers is underestimated. Externally, no, but internally, there&#039;s a lof of them...and they&#039;re likely all in the very soft underbelly of networks making them very juicy indeed...


Post the damned VERT solution. And yes, while I got your email, I just haven&#039;t had time or luck with that challenge. :\</description>
		<content:encoded><![CDATA[<p>There could be an insider case made as well. I know our DCs double as our internal-only DNS servers. This vuln in the DNS means our DCs could be popped internally. The only real solution (for us, I think) is to migrate DNS off the DCs. But that&#8217;s not something the team wants to do, so we&#8217;ll just wait for a patch. My IPS should notice this attack, thankfully.</p>
<p>I&#8217;d be curious if this turns into a worm. I think a worm that combines mass-mail along with internet/intranet scanning could be pretty damaging.</p>
<p>Code Red, no. But I think the number of Windows DNS servers is underestimated. Externally, no, but internally, there&#8217;s a lof of them&#8230;and they&#8217;re likely all in the very soft underbelly of networks making them very juicy indeed&#8230;</p>
<p>Post the damned VERT solution. And yes, while I got your email, I just haven&#8217;t had time or luck with that challenge. :\</p>
]]></content:encoded>
	</item>
</channel>
</rss>

