<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title><![CDATA[[SecurityRatty] tag: claims-aware]]></title>
    <link>http://securityratty.com/tag/claims-aware</link>
    <description></description>
    <pubDate>Mon, 06 Oct 2008 15:01:01 +0000</pubDate>
    <generator>iRatty Engine</generator>
    <docs>http://blogs.law.harvard.edu/tech/rss</docs>
    <item>
      <title><![CDATA[Vulnerabilities and Office Versions]]></title>
      <link>http://securityratty.com/article/33580f773ea9bcdfab98d5db31b1fd04</link>
      <guid>http://securityratty.com/article/33580f773ea9bcdfab98d5db31b1fd04</guid>
      <description><![CDATA[Most of the ink on Microsoft vulnerability coverage goes to browsers and operating systems, but in a way the best progress vulnerabilities have made has been in Microsoft Office. Some of the great...]]></description>
      <content:encoded><![CDATA[Most of the ink on Microsoft vulnerability coverage goes to browsers and operating systems, but in a way the best progress vulnerabilities have made has been in Microsoft Office. Some of the great attacks of all time (remember LoveLetter?) have been through Office bugs, and I believe most targeted attacks over the last few years have utilized vulnerabilities in Office document parsers.

That's why it's encouraging that Microsoft has done a much better job in making current versions of Office secure, as <a href="http://blogs.msdn.com/david_leblanc/archive/2008/11/17/improvements-in-office-security.aspx">David LeBlanc's recent blog shows</a>. He claims that the company has really stepped up the security testing for Office 2003 SP3 and Office 2007, and that it shows up in the number of reported vulnerabilities. The trend is clear: There are about half as many vulnerabilities as for earlier versions.

There may be a little flaw in the analysis in that LeBlanc studied reports during the period from 9/18/2007 to 11/17/2008. By that time earlier Office versions had been around for a long time and many vulnerabilities had already been reported on them. But even so, it makes the numbers all the more impressive for the new versions; the older ones had already had the low-hanging fruit picked clean and yet they still had CVE numbers in excess of the new ones. It seems there is no low-hanging vulnerability fruit in new versions of Office.

Are you running an old version of Office? Are you running Office 2003 SP2, which <a href="http://blogs.eweek.com/cheap_hack/content/office/office_2003_sp2_approaching_end_of_life.html">reached the end of support life in October</a>? If so, you are exposing yourself to more known threats than you may think.

Office versions are not plug-and-play interchangeable. It's unfortunate that Microsoft saw fit to accompany Office 2007's security enhancements with a radical user interface change. I personally have gotten used to it, but I can see an enterprise being intimidated by the training it would necessitate.

If you feel you're stuck in Office 2003, at the very least it's irresponsible to linger on in an old service pack. Do what you can to move on to SP3.
<p><a href="http://feedads.googleadservices.com/~at/4uM3tOE5mU12QfUHAZpBRMt2y_E/a"><img src="http://feedads.googleadservices.com/~at/4uM3tOE5mU12QfUHAZpBRMt2y_E/i" border="0" ismap="true"></img></a></p><img src="http://feedproxy.google.com/~r/RSS/cheap_hack/~4/cnC-qNVdwk4" height="1" width="1"/>]]></content:encoded>
      <pubDate>Mon, 01 Dec 2008 04:19:33 +0000</pubDate>
      <category domain="http://securityratty.com/tag/office versions">office versions</category>
      <category domain="http://securityratty.com/tag/office">office</category>
      <category domain="http://securityratty.com/tag/microsoft office">microsoft office</category>
      <category domain="http://securityratty.com/tag/versions">versions</category>
      <category domain="http://securityratty.com/tag/office secure">office secure</category>
      <category domain="http://securityratty.com/tag/office bugs">office bugs</category>
      <category domain="http://securityratty.com/tag/vulnerabilities">vulnerabilities</category>
      <category domain="http://securityratty.com/tag/office document parsers">office document parsers</category>
      <category domain="http://securityratty.com/tag/accompany office">accompany office</category>
      <source url="http://feeds.ziffdavisenterprise.com/~r/RSS/cheap_hack/~3/cnC-qNVdwk4/vulnerabilities_and_office_versions.html">Vulnerabilities and Office Versions</source>
    </item>
    <item>
      <title><![CDATA[Links List 11.17.08]]></title>
      <link>http://securityratty.com/article/85b0ee0a0390b793b97cc896d3067a94</link>
      <guid>http://securityratty.com/article/85b0ee0a0390b793b97cc896d3067a94</guid>
      <description><![CDATA[Wow. I think we all know that we can take or leave surveys numbers dont mean a lot without context. In this case the context is the current economic meltdown. The Society for Information Management...]]></description>
      <content:encoded><![CDATA[<p>Wow. I think we all know that we can take or leave surveys – numbers don’t mean a lot without context. In this case the “context” is the current economic meltdown. The Society for Information Management (SIM) released the results of their 2008 IT Trends Survey – predicting an “upbeat” forecast for IT jobs; the HUGE caveat here is that the study was conducted before all the recent economic woes. Apparently organizations are using IT to <a href="http://blogs.zdnet.com/BTL/?p=10765" target="_blank">drive efficiencies, streamline operations, and cut costs</a> rather than just slashing the IT budget to save money during the downturn. What would be a nice follow-up: a quick second survey comparing responses before and after. Regardless Jerry Luftman, SIM vice president of academic affairs, still says the survey results demonstrate “that the overall state of IT remains very strong.”</p>
<p><img style="margin: 5px" src="http://images.google.com/url?q=http://disney-clipart.com/Chicken-Little/Disney-Chicken-Little.jpg&amp;usg=AFQjCNGA4kajmvy1h_lrcRnuywgV7_X0aQ" alt="" width="198" height="201" align="left" />The sky is falling! Trip Chowdhry, the analyst with Global Equities Research who claimed Red Hat was ‘rubbish and the entire LAMP stack is potty, too’ published some eye-opening predictions, predominantly negative, about tech business in Silicon Valley. Now <a href="http://news.cnet.com/8301-13505_3-10094221-16.html?part=rss&amp;subj=news&amp;tag=2547-1_3-0-20" target="_blank">Chowdhry claims that “almost every VC funded open-source company</a> is struggling and will run out of money within the next six months.” (Probably not the most unbiased guy about open source) Matt Asay argues that organizations in general are struggling, but open-source companies are not that high on the list. (But are they high on the VC “axe” list??) He notes Alfresco, Pentaho and JasperSoft are some of the players with ‘millions in the bank and growing revenue.’ Asay also says Chowdhry has a responsibility to do real due diligence and not create myths. Take that, Chicken Little! (<a href="http://disney-clipart.com/Chicken-Little/Disney-Chicken-Little.jpg" target="_blank"><em>img from Disney-Clipart</em></a>)</p>
<p>We’re not as far behind as we thought we were. Google presented the results of a study they conducted about how IPv6- capable “ordinary users” are at the RIPE meeting in Dubai a few weeks ago. Turns out Apple Macs drive IPv6 penetration in the US. <a href="http://arstechnica.com/news.ars/post/20081113-google-more-macs-mean-higher-ipv6-usage-in-us.html" target="_blank">Fifty-two percent of all IPv6 users in the U.S. own a Mac</a> and use 6to4 (creating IPv6 addresses from an IPv4 address and tunneling packets) – making the US fifth in the list of countries using IPv6. Russia and France took first and second place with .76 and .65 percent IPv6-enabled traffic . The US is at .45 percent. Worldwide, 0.238 percent of Google users’ systems are IPv6-enabled and prefer to use IPv6 over IPv4.</p>
<p>Obama’s win = Google’s win? Apparently Google <a href="http://blogs.cioinsight.com/biztech30/content/2008_campaign/google_vs_microsoft_the_obama_factor.html?kc=rss" target="_blank">CEO Eric Schmidt and President-Elect Obama are very good buddies</a> and “this terrifies Microsoft”. Now competitors are more on guard against Google’s growing empire and popularity. Although Schmidt was mentioned as a possible candidate for the country’s new national CTO position, he said he would not accept the post if asked. I guess that’s one less thing Microsoft has to worry about.</p>
]]></content:encoded>
      <pubDate>Mon, 17 Nov 2008 19:35:52 +0000</pubDate>
      <category domain="http://securityratty.com/tag/list">list</category>
      <category domain="http://securityratty.com/tag/survey results">survey results</category>
      <category domain="http://securityratty.com/tag/results">results</category>
      <category domain="http://securityratty.com/tag/ipv6 addresses">ipv6 addresses</category>
      <category domain="http://securityratty.com/tag/ipv6">ipv6</category>
      <category domain="http://securityratty.com/tag/percent">percent</category>
      <category domain="http://securityratty.com/tag/open-source company">open-source company</category>
      <category domain="http://securityratty.com/tag/source">source</category>
      <category domain="http://securityratty.com/tag/fifty-two percent">fifty-two percent</category>
      <source url="http://blog.sciencelogic.com/links-list-111708/11/2008">Links List 11.17.08</source>
    </item>
    <item>
      <title><![CDATA[Modified Zeus Crimeware Kit Gets a Performance Boost]]></title>
      <link>http://securityratty.com/article/206d70045cec21b7f158d2fdc041b855</link>
      <guid>http://securityratty.com/article/206d70045cec21b7f158d2fdc041b855</guid>
      <description><![CDATA[Oops, they did it again - modifying an open source crimeware kit like Zeus in order to improve its performance, fix previously known bugs, and release the improved administration script for free at...]]></description>
      <content:encoded><![CDATA[<div style="text-align: left;"></div><div class="separator" style="clear: both; text-align: center;"></div><a href="http://3.bp.blogspot.com/_wICHhTiQmrA/SQ8K2EKd8NI/AAAAAAAACaE/UGYKyEUZBKs/s1600-h/modified_zeus_performance_admin.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" src="http://3.bp.blogspot.com/_wICHhTiQmrA/SQ8K2EKd8NI/AAAAAAAACaE/_DEokn56Kdo/s200-R/modified_zeus_performance_admin.png" /></a>Oops, they did it again - <a href="http://ddanchev.blogspot.com/2008/09/modified-zeus-crimeware-kit-comes-with.html">modifying an open source crimeware kit like Zeus</a> in order to improve its performance, fix previously known bugs, and release the improved administration script for free at the end of October.<br />
<br />
It's important to point out that both of these modifications haven't been released by <a href="http://www.usatoday.com/tech/news/computersecurity/2008-08-04-hacker-cybercrime-zeus-identity-theft_N.htm">the original author of Zeus</a>, but by third parties filling in the gaps he has left open. The very nature of open source web based malware exploitation kits is one of the key factors for the ongoing <a href="http://ddanchev.blogspot.com/2008/08/web-based-botnet-command-and-control.html">convergence of traffic management, exploits serving, ddos, and cybercrime as a service</a> features into a simplified cybercrime platform available on demand.<br />
<br />
Following the discovery of <a href="http://ddanchev.blogspot.com/2008/06/zeus-crimeware-kit-vulnerable-to.html">a remotely exploitable flaw within Zeus in June</a> -- a <a href="http://ddanchev.blogspot.com/2008/08/pinch-vulnerable-to-remotely.html">flaw affecting Pinch</a> leaked out two months later -- allowing cyberciminals to inject their own credentials and hijack the botnet of other cybercriminals, this modified version claims to have fixed three vulnerabilities within the original Zeus release, namely, a remote file inclusion flaw and two SQL injections within the administration panel. Here's the new CHANGELOG :<br />
<br />
"<i>- code improvements and optimizations<br />
- internal data checkings added<br />
- exit() function instead of die()<br />
- echo() function instead of print()<br />
- mysql_affected_rows () changed to mysql_num_rows () everywhere<br />
- all queries are fixed in system or mod .php files<br />
- no text password in the database and clear text password in $_SESSION, cookies authentication is gone and md5 hashes are everywhere<br />
- Geo IP support has been added <br />
- umask () bug fixed, the file has been created (chmoded) with different permissions<br />
- language improvements and pre-installation checks<br />
- checking for php version/safe_mod/open_basedir as you're required to run php 5.1.0 or higher to run it successfully<br />
<b>- fixed sql injection in credentials checking </b><br />
<b>- GetUserData () function has been rewritten - possible sql injection fixed</b><br />
<b>- possible remote file inclusion fixed</b><br />
- socket error definition changed<br />
- gcnt () function has been rewritten so you can use geolication - GeoIP which is free and GeoIPCity which is paid<br />
- ip address checking improved through validIP() function improvement<br />
- all queries are now fixed, input data has been sanitized<br />
- fs () function has been fixed in order to improve the quality of the log names<br />
- formatFilePath () function has been added for file upload purposes<br />
- arbitrary file upload bug has been fixed so that you can now upload only images with original names <br />
- the Log2SQL () function has been changed and stricter data checking/sanitizing is added<br />
- internal file sorting mechanism is improved so that files/dirs are sorted by file modification time</i>"<br />
<br />
As it's becoming increasingly clear that what once used to be a proprietary crimeware kits whose business model got undermined by their open source nature and the fact that they've started leaking for average cybercriminals and script kiddies to take advantage of, are today's "open source projects" - and therefore maintaining static lists of exploits and features included within a particular kit is getting even more irrelevant these days. In the long term, the quality assurance processes applied within crimeware kits courtesy of third party cybercriminals, is prone to shift from performance to <a href="http://ddanchev.blogspot.com/2008/10/quality-and-assurance-in-malware.html">improving the infection rates</a>.<div class="feedflare">
<a href="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?a=sKCIN"><img src="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?i=sKCIN" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?a=tB0JN"><img src="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?i=tB0JN" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?a=1XIkn"><img src="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?i=1XIkn" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?a=1XWUn"><img src="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?i=1XWUn" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?a=xmgXN"><img src="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?i=xmgXN" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?a=QpufN"><img src="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?i=QpufN" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?a=i4Nun"><img src="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?i=i4Nun" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/DanchoDanchevOnSecurityAndNewMedia/~4/441336309" height="1" width="1"/>]]></content:encoded>
      <pubDate>Mon, 03 Nov 2008 11:12:30 +0000</pubDate>
      <category domain="http://securityratty.com/tag/fixed">fixed</category>
      <category domain="http://securityratty.com/tag/sql injection fixed">sql injection fixed</category>
      <category domain="http://securityratty.com/tag/zeus">zeus</category>
      <category domain="http://securityratty.com/tag/fixed sql injection">fixed sql injection</category>
      <category domain="http://securityratty.com/tag/upload">upload</category>
      <category domain="http://securityratty.com/tag/file upload purposes">file upload purposes</category>
      <category domain="http://securityratty.com/tag/file">file</category>
      <category domain="http://securityratty.com/tag/function improvement">function improvement</category>
      <category domain="http://securityratty.com/tag/function">function</category>
      <source url="http://feeds.feedburner.com/~r/DanchoDanchevOnSecurityAndNewMedia/~3/441336309/modified-zeus-crimeware-kit-gets.html">Modified Zeus Crimeware Kit Gets a Performance Boost</source>
    </item>
    <item>
      <title><![CDATA[Harvard professor offers new challenge to RIAA anti-piracy campaign]]></title>
      <link>http://securityratty.com/article/61eede6bd594fe1e2f86d094bcd5086a</link>
      <guid>http://securityratty.com/article/61eede6bd594fe1e2f86d094bcd5086a</guid>
      <description><![CDATA[A Harvard law professor is trying a new tack to challenge the RIAA's anti-piracy campaign. Charles Nesson claims that the law the music industry group is using in its lawsuits is...]]></description>
      <content:encoded><![CDATA[A Harvard law professor is trying a new tack to challenge the RIAA's anti-piracy campaign. Charles Nesson claims that the law the music industry group is using in its lawsuits is unconstitutional.<br style="clear: both;"/>
    <a style='font-size: 10px; color: maroon;' href='http://www.pheedo.com/hostedMorselClick.php?hfmm=v3:ef069d32ab59b3fa80adc5e668a30530:o2nt6ZUgZN8B5VFiZYRyu9HKoSp%2F4irLCmY0jZgxcJMzQ2zhDU05gpiZeH0GDleWBxAOJsbyK%2B98'><img border='0' title='Add to digg' alt='Add to digg' src='http://www.pheedo.com/images/mm/digg.gif'/></a>
    <a style='font-size: 10px; color: maroon;' href='http://www.pheedo.com/hostedMorselClick.php?hfmm=v3:b77879df7beee09ea8031d795b73b7ad:ItO6LpTB3%2B73iFxc6vgaJ4efkrC%2BOMXJuDy1tBHSa3r6gOSY6K3aPbU7kuVeIRoeTO24QV58RG0bdg%3D%3D'><img border='0' title='Add to StumbleUpon' alt='Add to StumbleUpon' src='http://www.pheedo.com/images/mm/stumbleit.gif'/></a>
    <a style='font-size: 10px; color: maroon;' href='http://www.pheedo.com/hostedMorselClick.php?hfmm=v3:213c2a5ce2e3cb80f966839c609a8998:90DXJLK6Si9Hcc7nzs2hLINon5awzpXpNZQAfdWY9cZb7nwNR7VM%2FWOE12VWMbhAwdn7gvEtfI5Azg%3D%3D'><img border='0' title='Add to Twitter' alt='Add to Twitter' src='http://www.pheedo.com/images/mm/twitter.png'/></a>
    <a style='font-size: 10px; color: maroon;' href='http://www.pheedo.com/hostedMorselClick.php?hfmm=v3:973518bde6851d2eb259b179bd16d0a2:Y5%2BLKvgQKdUeXnFUlDOshR%2Bv4AGBBRZnLDGWxv7DuH7oxzbUvXCZL5dM8N7pK4gpmQ5EC80UpI0AGg%3D%3D'><img border='0' title='Add to Slashdot' alt='Add to Slashdot' src='http://www.pheedo.com/images/mm/slashdot.png'/></a>
<br style="clear: both;"/>      <a href="http://www.pheedo.com/feeds/ht.php?t=c&amp;i=55995ad038e1a3ba9942a6b657761e6c"><img src="http://www.pheedo.com/feeds/ht.php?t=v&amp;i=55995ad038e1a3ba9942a6b657761e6c" border="0" /></a>
  <img src="http://www.pheedo.com/feeds/tracker.php?i=55995ad038e1a3ba9942a6b657761e6c" style="display: none;" border="0" height="1" width="1" alt=""/>]]></content:encoded>
      <pubDate>Thu, 30 Oct 2008 01:00:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/law">law</category>
      <category domain="http://securityratty.com/tag/harvard law professor">harvard law professor</category>
      <category domain="http://securityratty.com/tag/anti-piracy campaign">anti-piracy campaign</category>
      <category domain="http://securityratty.com/tag/charles nesson claims">charles nesson claims</category>
      <category domain="http://securityratty.com/tag/music industry">music industry</category>
      <category domain="http://securityratty.com/tag/challenge">challenge</category>
      <category domain="http://securityratty.com/tag/riaa">riaa</category>
      <category domain="http://securityratty.com/tag/lawsuits">lawsuits</category>
      <category domain="http://securityratty.com/tag/tack">tack</category>
      <source url="http://feeds.computerworld.com/click.phdo?i=55995ad038e1a3ba9942a6b657761e6c">Harvard professor offers new challenge to RIAA anti-piracy campaign</source>
    </item>
    <item>
      <title><![CDATA[How can we co-operate to tackle phishing?]]></title>
      <link>http://securityratty.com/article/0b1c35bf86cb16980eeff0d57cfe4abb</link>
      <guid>http://securityratty.com/article/0b1c35bf86cb16980eeff0d57cfe4abb</guid>
      <description><![CDATA[Richard Clayton and I recently presented evidence of the adverse impact of take-down companies not sharing phishing feeds . Many phishing websites are missed by the take-down company which has the...]]></description>
      <content:encoded><![CDATA[<p><a href="http://www.cl.cam.ac.uk/~rnc1/">Richard Clayton</a> and <a href="http://people.seas.harvard.edu">I</a> recently presented <a href="http://www.lightbluetouchpaper.org/2008/10/16/non-cooperation-in-the-fight-against-phishing/">evidence of the adverse impact of take-down companies not sharing phishing feeds</a>.  Many phishing websites are missed by the take-down company which has the contract for removal; unsurprisingly, these websites are not removed very fast. Consequently, more consumers&#8217; identities are stolen.</p>
<p>In the <a href="http://people.seas.harvard.edu/~tmoore/ecrime08.pdf">paper</a>, we propose a simple solution: take-down companies should share their raw, unverified feeds of phishing URLs with their competitors.  Each company can examine the raw feed, pick out the websites impersonating their clients, and focus on removing these sites.</p>
<p>Since we presented our findings to the <a href="http://www.apwg.org">Anti-Phishing Working Group</a> <a href="http://www.ecrimeresearch.org/">eCrime Researchers Summit</a>, we have received considerable feedback from take-down companies.  Take-down companies attending the APWG meeting understood that sharing would help speed up response times, but expressed reservations at sharing their feeds unless they were duly compensated.  <a href="http://www.cyveillence.com/web/corporate/exec/olson.asp">Eric Olsen</a> of <a href="http://www.cyveillance.com">Cyveillance</a> (another company offering take-down services) has written a <a href="http://www.cyveillanceblog.com/phishing/a-contrary-perspective-–-forced-data-sharing-will-decrease-performance-and-reduce-protection">comprehensive rebuttal</a> of our recommendations.  He argues that competition between take-down companies drives investment in efforts to detect more websites. Mandated sharing of phishing URL feeds, in his view, would undermine these detection efforts and cause take-down companies such as Cyveillance to exit the business.</p>
<p>I do have some sympathy for the objections raised by the take-down companies.  As we state in the paper, <a href="http://en.wikipedia.org/wiki/Free_rider_problem">free-riding</a> (where one company relies on another to invest in detection so they don&#8217;t have to) is a concern for any sharing regime.  Academic research studying other areas of information security (e.g., <a href="http://papers.ssrn.com/sol3/papers.cfm?abstract_id=1000369">here</a> and <a href="http://ideas.repec.org/p/wpa/wuwpio/0503004.html">here</a>), however, has shown that free-riding is unlikely to be so rampant as to drive all the best take-down companies out of offering service, as Mr. Olsen suggests.</p>
<p>While we can quibble over the extent of the threat from free free-riding, it should not detract from the conclusions we draw over the need for greater sharing.  In our view, it would be unwise and irresponsible to accept the current status quo of keeping phishing URL feeds completely private.  After all, competition without sharing has approximately <em>doubled</em> the lifetimes of phishing websites!  The solution, then, is to devise a sharing mechanism that gives take-down companies the incentive to keep detecting more phishing URLs.<br />
<span id="more-469"></span><br />
Here is our stab at devising a suitable sharing mechanism.  We propose the creation of a members-only sharing club with compensation for net contributors paid for by net receivers. Take-down companies submit real-time copies of their entire feeds to a trusted third party (for the sake of argument, let&#8217;s assume that the <a href="http://www.apwg.org">APWG</a> takes on this role).  The APWG collates the individual feeds, marks the source of each submission (i.e., which take-down company) along with a timestamp.  The APWG makes the amalgamated feed available immediately to all members.  The members pick out phishing URLs impersonating their own clients, while ignoring the rest.  Crucially, the expensive task of verifying phishing URLs and initiating take-down continues to be performed by the take-down company. </p>
<p>Periodically, the combined feed is audited to determine the reciprocity of contributions.  Take-down companies provide a list of their clients to the auditor.  The auditor then computes the number of phishing websites impersonating each take-down company&#8217;s clients that are missed by the takedown company but identified by others.  The auditor also tallies the time difference for phishing websites  that are identified by others first.</p>
<p>For example, suppose bank A1 has hired take-down company A to remove phishing sites on its behalf, and bank B1 has hired take-down company B.  Suppose 500 phishing sites impersonate A1, and that A identifies 400 while B identifies an additional 100 sites missed by A.  Likewise, suppose another 500 phishing sites impersonate bank B1, and that B identifies 300 while A identifies an additional 200 sites missed by B. B has received a net of 100 useful phishing sites more from A than B has given to A.  Consequently, B should pay A a previously-agreed &#8216;finder&#8217;s fee&#8217; for identifying these extra 100 websites. </p>
<p>The &#8216;finder&#8217;s fee&#8217; provides additional incentive for take-down companies to invest in better phishing website detection. Designed properly, such a sharing club can overcome the potential for free-riding that companies such as Cyveillance fret about, while increasing sharing to shorten phishing website lifetimes. </p>
<p>Some subtleties must be mentioned, however.  If the finder&#8217;s fee is big enough, some companies may be tempted to cheat to minimize their payout.  For instance, underperforming take-down companies could claim to have independently discovered missing data from their feed shortly after collecting it from the shared feed.  This can be mitigated by adding a credible threat of detection &#8212; inserting a few dubious fake phishing URLs that only appear in the shared feed.  If the company claims to have &#8216;independently&#8217; rediscovered these URLs, then they will be caught cheating.  Another issue is that the auditing system does incur some overhead, which could be avoided if sharing was made unconditional.  </p>
<p>To sum up, we recognize that many take-down companies will be reticent to share.  However, we feel that sharing is too important to the goal of tackling phishing to brush aside because of a few inevitable complications.  For the good of protecting consumers, the anti-phishing industry should learn to co-operate!</p>
]]></content:encoded>
      <pubDate>Mon, 27 Oct 2008 09:47:06 +0000</pubDate>
      <category domain="http://securityratty.com/tag/companies">companies</category>
      <category domain="http://securityratty.com/tag/take-down companies provide">take-down companies provide</category>
      <category domain="http://securityratty.com/tag/hired take-down company">hired take-down company</category>
      <category domain="http://securityratty.com/tag/take-down company">take-down company</category>
      <category domain="http://securityratty.com/tag/take-down companies">take-down companies</category>
      <category domain="http://securityratty.com/tag/company">company</category>
      <category domain="http://securityratty.com/tag/feeds">feeds</category>
      <category domain="http://securityratty.com/tag/entire feeds">entire feeds</category>
      <category domain="http://securityratty.com/tag/url feeds completely">url feeds completely</category>
      <source url="http://www.lightbluetouchpaper.org/2008/10/27/how-can-we-co-operate-to-tackle-phishing/">How can we co-operate to tackle phishing?</source>
    </item>
    <item>
      <title><![CDATA[Exclusive: Russian Coder Says He Hacked Georgia Sites in Cyberwar]]></title>
      <link>http://securityratty.com/article/06c82af5a1163a1dcc30769948169453</link>
      <guid>http://securityratty.com/article/06c82af5a1163a1dcc30769948169453</guid>
      <description><![CDATA[Government and independent investigators are still trying to figure out who, exactly, hit Georgia's websites during its August war with Russia. Now, one of the hackers who claims to be behind some of...]]></description>
      <content:encoded><![CDATA[Government and independent investigators are still trying to figure
out who, exactly, hit Georgia's websites during its August war with
Russia. Now, one of the hackers who claims to be behind some of the
cyber attacks is telling all.<br style="clear: both;"/>
  <img alt="" style="border: 0; height:1px; width:1px;" border="0" src="http://www.pheedo.com/img.phdo?i=3506f578a4fa4534344393b609da7166" height="1" width="1"/>
<img src="http://www.pheedo.com/feeds/tracker.php?i=3506f578a4fa4534344393b609da7166" style="display: none;" border="0" height="1" width="1" alt=""/><div class="feedflare">
<a href="http://feeds.feedburner.com/~f/wired/politics/privacy?a=nXaDM"><img src="http://feeds.feedburner.com/~f/wired/politics/privacy?i=nXaDM" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/wired/politics/privacy?a=NOsJm"><img src="http://feeds.feedburner.com/~f/wired/politics/privacy?i=NOsJm" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/wired/politics/privacy?a=TnEbm"><img src="http://feeds.feedburner.com/~f/wired/politics/privacy?i=TnEbm" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/wired/politics/privacy?a=LaLcM"><img src="http://feeds.feedburner.com/~f/wired/politics/privacy?i=LaLcM" border="0"></img></a>
 <a href="http://feeds.wired.com/~f/wired/politics/security?a=c8SFM"><img src="http://feeds.wired.com/~f/wired/politics/security?i=c8SFM" border="0"></img></a> <a href="http://feeds.wired.com/~f/wired/politics/security?a=Dewsm"><img src="http://feeds.wired.com/~f/wired/politics/security?i=Dewsm" border="0"></img></a> <a href="http://feeds.wired.com/~f/wired/politics/security?a=zDpxm"><img src="http://feeds.wired.com/~f/wired/politics/security?i=zDpxm" border="0"></img></a> <a href="http://feeds.wired.com/~f/wired/politics/security?a=KYUAM"><img src="http://feeds.wired.com/~f/wired/politics/security?i=KYUAM" border="0"></img></a> </div><img src="http://feeds.feedburner.com/~r/wired/politics/privacy/~4/429923777" height="1" width="1"/><img src="http://feeds.wired.com/~r/wired/politics/security/~4/429923789" height="1" width="1"/>]]></content:encoded>
      <pubDate>Thu, 23 Oct 2008 14:07:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/independent investigators">independent investigators</category>
      <category domain="http://securityratty.com/tag/cyber attacks">cyber attacks</category>
      <category domain="http://securityratty.com/tag/hit georgia">hit georgia</category>
      <category domain="http://securityratty.com/tag/august war">august war</category>
      <category domain="http://securityratty.com/tag/russia">russia</category>
      <category domain="http://securityratty.com/tag/figure">figure</category>
      <category domain="http://securityratty.com/tag/government">government</category>
      <category domain="http://securityratty.com/tag/claims">claims</category>
      <category domain="http://securityratty.com/tag/websites">websites</category>
      <source url="http://feeds.wired.com/~r/wired/politics/security/~3/429923789/government-and.html">Exclusive: Russian Coder Says He Hacked Georgia Sites in Cyberwar</source>
    </item>
    <item>
      <title><![CDATA[FBI Announces They Operated and Closed the Dark Market Site]]></title>
      <link>http://securityratty.com/article/d41d35e862df52fd061da3218e9f9e38</link>
      <guid>http://securityratty.com/article/d41d35e862df52fd061da3218e9f9e38</guid>
      <description><![CDATA[Something rings strange to me in these reports of the Feds having operated a forum and marketplace site for hackers, Dark Market. The article in Wired claims the Feds were tracking hackers movements...]]></description>
      <content:encoded><![CDATA[<p>Something rings strange to me in <a rel="nofollow" target="_blank" href="http://blog.wired.com/27bstroke6/2008/10/darkmarket-post.html">these reports</a> of the Feds having operated a forum and marketplace site for hackers, Dark Market. The article in Wired claims the Feds were tracking hacker&#8217;s movements and acquiring intelligence so they could perform a sting operation and catch the criminals. Then they closed the site and publicly announced their involvement with it:</p>
<blockquote><p>The FBI almost certainly closed DarkMarket in preparation for a global wave of arrests that will unfold in the next month or so. The site was likely shuttered to avoid an Agatha Christie scenario in which a diminishing pool of cybercrooks are free to speculate about why they&#8217;re disappearing one-by-one like the hapless dinner guests in <em>Ten Little Indians</em>.</p></blockquote>
<p>How on Earth does that make sense? If they close the market and announce their involvement, now they&#8217;ve given up their cover and surely all the hackers already know the FBI is on to them. They can simply move and restart their operations somewhere else.</p>
<p>Read the whole <a rel="nofollow" target="_blank" href="http://blog.wired.com/27bstroke6/2008/10/darkmarket-post.html">Wired article </a>here.</p>]]></content:encoded>
      <pubDate>Wed, 15 Oct 2008 07:00:31 +0000</pubDate>
      <category domain="http://securityratty.com/tag/site">site</category>
      <category domain="http://securityratty.com/tag/market">market</category>
      <category domain="http://securityratty.com/tag/dark market">dark market</category>
      <category domain="http://securityratty.com/tag/fbi">fbi</category>
      <category domain="http://securityratty.com/tag/marketplace site">marketplace site</category>
      <category domain="http://securityratty.com/tag/hackers movements">hackers movements</category>
      <category domain="http://securityratty.com/tag/hackers">hackers</category>
      <category domain="http://securityratty.com/tag/hapless dinner guests">hapless dinner guests</category>
      <category domain="http://securityratty.com/tag/agatha christie scenario">agatha christie scenario</category>
      <source url="http://feeds.feedburner.com/~r/itsecurity/~3/421823951/">FBI Announces They Operated and Closed the Dark Market Site</source>
    </item>
    <item>
      <title><![CDATA[Uncommon Assurance With Common Criteria]]></title>
      <link>http://securityratty.com/article/6239b9efa09233bac59212ea9028a9a6</link>
      <guid>http://securityratty.com/article/6239b9efa09233bac59212ea9028a9a6</guid>
      <description><![CDATA[Corporations spend millions of dollars in getting their products Common Criteria-certified. It is a validation of being tested per an international security evaluation standard for meeting stated...]]></description>
      <content:encoded><![CDATA[<p>Corporations spend millions of dollars in getting their products Common Criteria-certified. It is a validation of being tested per an international security evaluation standard for meeting stated security claims.  Yet, the claims made by companies are not mandated to be at rigorous security levels by the Common Criteria standard &mdash; it merely advocates thorough testing. </p>]]></content:encoded>
      <pubDate>Tue, 14 Oct 2008 20:00:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/common criteria standard">common criteria standard</category>
      <category domain="http://securityratty.com/tag/claims">claims</category>
      <category domain="http://securityratty.com/tag/security claims">security claims</category>
      <category domain="http://securityratty.com/tag/rigorous security levels">rigorous security levels</category>
      <category domain="http://securityratty.com/tag/products common">products common</category>
      <category domain="http://securityratty.com/tag/companies">companies</category>
      <category domain="http://securityratty.com/tag/validation">validation</category>
      <category domain="http://securityratty.com/tag/corporations">corporations</category>
      <category domain="http://securityratty.com/tag/millions">millions</category>
      <source url="http://www.rsa.com/blog/blog_entry.aspx?id=1367">Uncommon Assurance With Common Criteria</source>
    </item>
    <item>
      <title><![CDATA[Debunking the Latest Fear Mongering News on WPA security]]></title>
      <link>http://securityratty.com/article/db5c2f6d20bfbc204064e7ebc539557c</link>
      <guid>http://securityratty.com/article/db5c2f6d20bfbc204064e7ebc539557c</guid>
      <description><![CDATA[I had been meaning to write about recent exaggerated claims that WPA security had been hacked, but George Ou beat me to it . The buzz comes from Elcomsoft's Distributed Password Recovery . The...]]></description>
      <content:encoded><![CDATA[I had been meaning to write about recent exaggerated claims that WPA security had been hacked, but <a href="http://www.formortals.com/Home/tabid/36/EntryID/119/Default.aspx">George Ou beat me to it</a>.

The buzz comes from <a href="http://www.elcomsoft.com/edpr.html">Elcomsoft's Distributed Password Recovery</a>. The innovation is that they use NVIDIA GPU acceleration for password cracking and can distribute the crack across a network to multiple clients and their NVIDIA GPUs. The GPU acceleration, they claim, "reduces password recovery time by a factor of 20."

They also take the unfortunate approach, <a href="http://www.elcomsoft.com/PR/edpr_081009_en.pdf">in a press release</a>, of massive gains in cracking WPA and WPA2 protection, and that they can "...break Wi-Fi encryption up to 100 times faster than by using CPU only."

100 times! 2 orders of magnitude! That must be a lot, right? Well, probably not. This is where George Ou calls shenanigans.

First, he points out that this only affects password protection systems that rely on password complexity, and that, as a general rule, the time involved is proportional to the complexity of the password. So if your password would normally take a million years to crack, it would take 10,000 years with this system. Draw your own conclusions.

He also points out, just to get past the WPA buzzwordism, that this is a more general attack mechanism and could, for example, be used against certain VPN systems.

With respect to WPA/WPA2 specifically, the attack is generally useful only against home users, because they are generally the ones using PSK (Private Shared Key) authentication. "It has zero affect enterprise mode WPA deployments which use TLS protected authentication such as PEAP or EAP-TLS. Internal LAN authentication schemes such as NTLM and LDAP are also significantly weakened.  SSL authentication schemes are not vulnerable to this particular attack."

If you are relying on password complexity for protection then his advice, and mine, is old news: first, if you're a business, perhaps you should be using a TLS-based authentication system. Also, you should make sure that your passwords are sufficiently complex and changed often enough. Ou has some specific advice about this in his column, but as he says, there are usually easier ways to get passwords (like offering people chocolate for them) than to spend years cracking them with thousands of dollars of computing power.
<p><a href="http://feedads.googleadservices.com/~a/OvpRctfZEnjDyyEg3MByesn2KpY/a"><img src="http://feedads.googleadservices.com/~a/OvpRctfZEnjDyyEg3MByesn2KpY/i" border="0" ismap="true"></img></a></p><img src="http://feedproxy.google.com/~r/RSS/cheap_hack/~4/zhaPa_33ZEQ" height="1" width="1"/>]]></content:encoded>
      <pubDate>Mon, 13 Oct 2008 05:07:51 +0000</pubDate>
      <category domain="http://securityratty.com/tag/wpa">wpa</category>
      <category domain="http://securityratty.com/tag/password">password</category>
      <category domain="http://securityratty.com/tag/password recovery">password recovery</category>
      <category domain="http://securityratty.com/tag/password complexity">password complexity</category>
      <category domain="http://securityratty.com/tag/authentication">authentication</category>
      <category domain="http://securityratty.com/tag/authentication system">authentication system</category>
      <category domain="http://securityratty.com/tag/complexity">complexity</category>
      <category domain="http://securityratty.com/tag/wpa security">wpa security</category>
      <category domain="http://securityratty.com/tag/nvidia gpu acceleration">nvidia gpu acceleration</category>
      <source url="http://feeds.ziffdavisenterprise.com/~r/RSS/cheap_hack/~3/zhaPa_33ZEQ/debunking_the_latest_fear_mongering_news_on_wpa_security.html">Debunking the Latest Fear Mongering News on WPA security</source>
    </item>
    <item>
      <title><![CDATA[Fake Windows XP Activation Trojan Wants Your CVV2 Code]]></title>
      <link>http://securityratty.com/article/fac8ba92dd4114941015e75bba3149c4</link>
      <guid>http://securityratty.com/article/fac8ba92dd4114941015e75bba3149c4</guid>
      <description><![CDATA[In a self-contradicting social engineering attempt, a malware author is offering to sale a ( updated version of Kardphisher) DIY fake Windows XP activation builder, which despite the fact that it...]]></description>
      <content:encoded><![CDATA[<div style="text-align: left;"></div><div class="separator" style="clear: both; text-align: center;"></div><a href="http://3.bp.blogspot.com/_wICHhTiQmrA/SOqbO7J3tvI/AAAAAAAACPg/YNDy4vo817c/s1600-h/fake_windows_xp_activation1.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" src="http://3.bp.blogspot.com/_wICHhTiQmrA/SOqbO7J3tvI/AAAAAAAACPg/BYpcW4rkU0o/s200-R/fake_windows_xp_activation1.png" /></a>In a self-contradicting social engineering attempt, a malware author is offering to sale a (<a href="http://www.symantec.com/security_response/writeup.jsp?docid=2007-042705-0108-99">updated version</a> of Kardphisher) DIY fake Windows XP activation builder, which despite the fact that it claims "<i>We will ask for your billing details, but your credit card will NOT be charged</i>", is requesting and remotely uploading all the credit card details required for a successfully credit card theft.<br />
<br />
Perhaps among the main reasons why such simplistic social engineering attempts never scaled in a "malicious economies of scale" approach, is because sophisticated crimeware kits capable of obtaining the very same data automatically, started leaking for everyone to start taking advantage of - including yesterday's cybercriminals using such DIY fake message builders. <br />
<br />
<div style="text-align: left;"></div><div class="separator" style="clear: both; text-align: center;"></div>Moreover, according to <a href="http://news.ncsu.edu/news/2008/09/wmswogalterfakemessage.php">recently reseased survey results</a>, end users cannot distinguish between fake popups and real ones, and on their way to continue doing what they were doing, click OK on that pesky warning message telling them that they're about to get infected with malware. Taking into consideration the fact that the popup windows the researchers used look like cheap creative compared to the average fake security software's layout high quality GUIs, it is perhaps worth restating your research questions with something in the lines of - <b>What motivates end users to install an antivirus application going under the name of Super Antivirus 2009 or Mega Virus Cleaner 2008?</b> The fact that the fake status bar is telling them that they're infected with 47 spyware cookies, or the fact that they ended up at the fake site while browsing their trusted web services? <br />
<br />
<a href="http://1.bp.blogspot.com/_wICHhTiQmrA/SOqf_xbxL7I/AAAAAAAACPo/6uvXj2AuS_A/s1600-h/fake_windows_xp_activation2.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" src="http://1.bp.blogspot.com/_wICHhTiQmrA/SOqf_xbxL7I/AAAAAAAACPo/fa1jUBjFGOU/s200-R/fake_windows_xp_activation2.png" /></a>The increase of <a href="http://ddanchev.blogspot.com/2008/09/diverse-portfolio-of-fake-security_30.html">rogue security software domains</a> is happening due to the high payout affiliation based model, the standardized creative allowing the participants to come up with their own fake names if they want to, and due to the fact that the fake security threats scareware approach seems to be perfectly taking advantage of the overall suspicion on the effectiveness of their legitimate security software.<div class="feedflare">
<a href="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?a=mw30M"><img src="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?i=mw30M" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?a=WJFzM"><img src="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?i=WJFzM" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?a=jNfpm"><img src="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?i=jNfpm" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?a=9lodm"><img src="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?i=9lodm" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?a=6go3M"><img src="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?i=6go3M" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?a=TLsPM"><img src="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?i=TLsPM" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?a=JuYBm"><img src="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?i=JuYBm" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/DanchoDanchevOnSecurityAndNewMedia/~4/413264124" height="1" width="1"/>]]></content:encoded>
      <pubDate>Mon, 06 Oct 2008 15:01:01 +0000</pubDate>
      <category domain="http://securityratty.com/tag/credit card details">credit card details</category>
      <category domain="http://securityratty.com/tag/credit card">credit card</category>
      <category domain="http://securityratty.com/tag/credit card theft">credit card theft</category>
      <category domain="http://securityratty.com/tag/details">details</category>
      <category domain="http://securityratty.com/tag/malware">malware</category>
      <category domain="http://securityratty.com/tag/malware author">malware author</category>
      <category domain="http://securityratty.com/tag/social">social</category>
      <category domain="http://securityratty.com/tag/mega virus cleaner">mega virus cleaner</category>
      <category domain="http://securityratty.com/tag/creative">creative</category>
      <source url="http://feeds.feedburner.com/~r/DanchoDanchevOnSecurityAndNewMedia/~3/413264124/fake-windows-xp-activation-trojan-wants.html">Fake Windows XP Activation Trojan Wants Your CVV2 Code</source>
    </item>
  </channel>
</rss>
