<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" 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/"><channel><title>Don't trust that data!</title><link>http://blogs.msdn.com/ptorr/archive/2004/04/12/111342.aspx</link><description>A while ago I wrote a couple of blog entries on code repurposing and some mitigations , and one of the main causes of that problem is that developers inherently trust data. The text box caption says Name , so it's always gonna contain the user's name,</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Don't trust that data!</title><link>http://blogs.msdn.com/ptorr/archive/2004/04/12/111342.aspx#112056</link><pubDate>Tue, 13 Apr 2004 06:22:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:112056</guid><dc:creator>Eric Carter</dc:creator><description>It seems to me that the attack doesn't even have to be even so sophisticated as to involve formulas and certainly doesn’t need to involve code.&lt;br&gt; &lt;br&gt;If some script on the server is grabbing data out of the spreadsheet, it is going to want to look in a particular location of the spreadsheet to get the data.&lt;br&gt;&lt;br&gt;There are two ways I know of for the script to grab this data out of the spreadsheet.  First, you create a named range--for example &amp;quot;ExpenseAmount&amp;quot; maps to Sheet1!$A$5..  Second, you do it based on absolute adress, just Sheet1!$A$5.  &lt;br&gt;&lt;br&gt;Either of these can be subverted.  For a named range, users can just edit the name of the range to point to something else--say Sheet3!$ZZ$3000.  Then they put into the Sheet1!$A$5 the reasonable expense and into Sheet3!$ZZ$3000 the unreasonable one that no one--except the script on the server--will look at.&lt;br&gt;&lt;br&gt;If the script is grabbing data out of the spreadsheet based on an absolute location, the attacker just has to hide column A and replace it with a column B.  With the unreasonable number in the hidden column A and the reasonable number in the unhidden column B, once again the same attack is enabled without any real fanciness.  If you want to get fancy, you can hide the row and column headers in Excel so you wouldn't be able to even detect this attack.&lt;br&gt;&lt;br&gt;It seems like launching an attack via cached data is the hardest of all possible attacks because you actually have to write a bunch of code to do so.&lt;br&gt;&lt;br&gt;Also, I wonder if document protection in Excel/Word could be used to provide a secure UI.  It sure seems unfortunate to have to display a WinForm to show your Excel data.</description></item><item><title>Follow up to </title><link>http://blogs.msdn.com/ptorr/archive/2004/04/12/111342.aspx#112405</link><pubDate>Tue, 13 Apr 2004 20:19:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:112405</guid><dc:creator>Office Development, Security, Randomness...</dc:creator><description /></item></channel></rss>