<?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: Rich Text Malware</title>
	<atom:link href="http://blogs.mcafee.com/mcafee-labs/2007/05/25/rich-text-malware/feed" rel="self" type="application/rss+xml" />
	<link>http://blogs.mcafee.com/mcafee-labs/rich-text-malware</link>
	<description></description>
	<lastBuildDate>Tue, 29 Nov 2011 07:51:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: john keane</title>
		<link>http://blogs.mcafee.com/mcafee-labs/rich-text-malware/comment-page-1#comment-10121</link>
		<dc:creator>john keane</dc:creator>
		<pubDate>Wed, 03 Sep 2008 22:20:57 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.mcafee.com/2007/05/25/rich-text-malware/#comment-10121</guid>
		<description>rtf is an open standard markup language and has no need to transfer executable code to satisfy its basic mapping function: font,upper-lower case, etc..

Why do such WPML + executable code programs such as MSWord not simply refuse to remap executable code from a default rtf-A standard.</description>
		<content:encoded><![CDATA[<p>rtf is an open standard markup language and has no need to transfer executable code to satisfy its basic mapping function: font,upper-lower case, etc..</p>
<p>Why do such WPML + executable code programs such as MSWord not simply refuse to remap executable code from a default rtf-A standard.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Graham</title>
		<link>http://blogs.mcafee.com/mcafee-labs/rich-text-malware/comment-page-1#comment-10120</link>
		<dc:creator>Mike Graham</dc:creator>
		<pubDate>Tue, 29 May 2007 21:33:48 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.mcafee.com/2007/05/25/rich-text-malware/#comment-10120</guid>
		<description>&gt;This was a problem with IE 5, Outlook Express 5, and Outlook
&gt;2000 until Microsoft patched it.

self edit:  this was a problem because IE &amp; OE would execute files directly into memory, therefore no virus scanner would get a chance to scan it first.</description>
		<content:encoded><![CDATA[<p>&gt;This was a problem with IE 5, Outlook Express 5, and Outlook<br />
&gt;2000 until Microsoft patched it.</p>
<p>self edit:  this was a problem because IE &amp; OE would execute files directly into memory, therefore no virus scanner would get a chance to scan it first.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Graham</title>
		<link>http://blogs.mcafee.com/mcafee-labs/rich-text-malware/comment-page-1#comment-10119</link>
		<dc:creator>Mike Graham</dc:creator>
		<pubDate>Tue, 29 May 2007 21:28:55 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.mcafee.com/2007/05/25/rich-text-malware/#comment-10119</guid>
		<description>most, if not all virus scanners do not scan files executed directly into memory; they must be run from the hard drive to be detected.  This was a problem with IE 5, Outlook Express 5, and Outlook 2000 until Microsoft patched it.

So, if Wordpad executes its attachment straight into memory, from within the .rtf already running in memory, then any virus infected process won&#039;t be noticed until it tries to write infected code to the hard drive.

my 1 1/3 cents</description>
		<content:encoded><![CDATA[<p>most, if not all virus scanners do not scan files executed directly into memory; they must be run from the hard drive to be detected.  This was a problem with IE 5, Outlook Express 5, and Outlook 2000 until Microsoft patched it.</p>
<p>So, if Wordpad executes its attachment straight into memory, from within the .rtf already running in memory, then any virus infected process won&#8217;t be noticed until it tries to write infected code to the hard drive.</p>
<p>my 1 1/3 cents</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Randy Abrams</title>
		<link>http://blogs.mcafee.com/mcafee-labs/rich-text-malware/comment-page-1#comment-10118</link>
		<dc:creator>Randy Abrams</dc:creator>
		<pubDate>Tue, 29 May 2007 14:37:59 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.mcafee.com/2007/05/25/rich-text-malware/#comment-10118</guid>
		<description>But every scanner&#039;s on-access module will block the eicar file when you extract it from the RTF. RTF may get known malware passed the email scanner, but not the on-access or reat-time scanner. This is really FUD. Scanning through RTF does not increase user secuirty. Blocking executable threats does. The threat is not executable until extracted from the RTF. It is no different than putting a k nown threat inside of an archive file that McAfee doesn&#039;t know. As soon as the user extracts the file it is detected.

Cheers,

Randy</description>
		<content:encoded><![CDATA[<p>But every scanner&#8217;s on-access module will block the eicar file when you extract it from the RTF. RTF may get known malware passed the email scanner, but not the on-access or reat-time scanner. This is really FUD. Scanning through RTF does not increase user secuirty. Blocking executable threats does. The threat is not executable until extracted from the RTF. It is no different than putting a k nown threat inside of an archive file that McAfee doesn&#8217;t know. As soon as the user extracts the file it is detected.</p>
<p>Cheers,</p>
<p>Randy</p>
]]></content:encoded>
	</item>
</channel>
</rss>

