<?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: peds]]></title>
    <link>http://securityratty.com/tag/peds</link>
    <description></description>
    <pubDate>Tue, 26 Feb 2008 17:33:32 +0000</pubDate>
    <generator>iRatty Engine</generator>
    <docs>http://blogs.law.harvard.edu/tech/rss</docs>
    <item>
      <title><![CDATA[Trusted path]]></title>
      <link>http://securityratty.com/article/3715e16ad56aac54a711e8dc12195a97</link>
      <guid>http://securityratty.com/article/3715e16ad56aac54a711e8dc12195a97</guid>
      <description><![CDATA[Trusted path is quite a common term in security research. It is the basis of many security protocol and application designs, and a security breach of it is one of the most common attack vectors
This...]]></description>
      <content:encoded><![CDATA[<p><a href="http://en.wikipedia.org/wiki/Trusted_path">Trusted path</a> is quite a common term in security research. It is the basis of many security protocol and application designs, and a security breach of it is one of the most common attack vectors.</p>

<p>This week, the Security Group <a href="http://www.cl.cam.ac.uk/research/security/banking/ped/">published their findings</a> on the vulnerability of PIN entry devices (PEDs) currently deployed in the UK (details available in their <a href="http://www.cl.cam.ac.uk/techreports/UCAM-CL-TR-711.pdf">technical report</a>). The vulnerability arises partially from insufficient protection of the PEDs from tampering and partially from communications between the card and the device not being encrypted. This effectively breaks the trusted path between customer's card and the retailer's terminal/card processing network. <em>You can <a href="http://video.google.com/videoplay?docid=-2532888875266883498">watch the BBC Newsnight program</a> covering this.</em></p>

<p>This week we (<a href="http://www.cronto.com/">Cronto</a>) have also made an <a href="http://www.cronto.com/cronto_finds_weaknesses.htm">announcement</a> about potential vulnerabilities of Chip and PIN based authentication for online banking. Whilst the CAP readers deployed by the UK banks can provide <a href="http://blog.cronto.com/index.php?title=transaction_verification_can_protect_aga">transaction authentication</a>, there is still a weak link. If the user is tricked into entering incorrect details into the CAP reader then they could be inadvertently authorising a fraudulent transaction. Whilst the possibility of this happening might seem remote, our analysis of existing systems shows otherwise. Again, the threats arise because there is no trusted path from the bank to the user's card/reader as the attacker can manipulate the presentation of the bank's website to the user.</p>

<p>The trusted path issue is common to all consumer payments industry applications: from ATMs with added PIN pads and tampered retail terminals to man-in-the-browser'ed banking websites. The problem is also increasing with the growth of the payments industry, and any potentially successful solution requires a new approach based on innovation rather than attempts to patch the holes in the old protocols.</p>

<p>These issues are already a subject of both academic research and commercial product development. Some see a solution in the <a href="http://mjj29.matthew.ath.cx/2007-Johnson-ebanking.pdf">USB tokens with strong security protocols</a>, some suggest <a href="http://blog.masabi.com/2007/09/two-factor-authentication-2fa.html">the mobile phone based PKI certificates</a> are the answer. At Cronto, we believe the <a href="http://www.cronto.com/technology.htm">visual channel</a> is the best way to go.</p>

<p><font color="#868686"><em>&lt;!-- If you are offended by a commercial company being passionate about its product and advocating innovation in a traditionally very conservative industry, you can stop reading now --&gt;</em></font></p>

<p>We believe that our visual cryptogram can provide a trusted path from a bank to the customer in the way which is both secure and simple for consumers.</p>
<div class="image_block"><img src="http://blog.cronto.com/media/blogs/uos/cronto-visual-cryptogram.gif" alt="Cronto Visual Cryptogram" title="" width="500" height="383" /></div><p> <br />
We chose the visual channel for the following reasons:</p>

<ul>
  <li>The image can contain encrypted data</li>
  <li>Most end user terminals can display images: from ATMs to Train Ticket machines to websites, no hardware modifications are needed</li>
  <li>Taking a picture of the terminal is easy for the user</li>
  <li>Any personal device can be used: a camera phone, a dedicated camera token or, potentially, a CAP reader, and even a credit card itself extended with a camera and our algorithms running on the chip</li>
  <li>Both attack vectors &ndash; the data in transfer being tampered with, and the user typing incorrect information &ndash; are mitigated</li>
</ul>



]]></content:encoded>
      <pubDate>Fri, 04 Apr 2008 17:18:17 +0000</pubDate>
      <category domain="http://securityratty.com/tag/path">path</category>
      <category domain="http://securityratty.com/tag/security">security</category>
      <category domain="http://securityratty.com/tag/security protocol">security protocol</category>
      <category domain="http://securityratty.com/tag/strong security protocols">strong security protocols</category>
      <category domain="http://securityratty.com/tag/protocols">protocols</category>
      <category domain="http://securityratty.com/tag/user">user</category>
      <category domain="http://securityratty.com/tag/user terminals">user terminals</category>
      <category domain="http://securityratty.com/tag/common">common</category>
      <category domain="http://securityratty.com/tag/attack vectors">attack vectors</category>
      <source url="http://blog.cronto.com/index.php?title=trusted_path&amp;more=1&amp;c=1&amp;tb=1&amp;pb=1">Trusted path</source>
    </item>
    <item>
      <title><![CDATA[Chip & PIN terminals vulnerable to simple attacks]]></title>
      <link>http://securityratty.com/article/81559287e233424259b25f0bd4b724e4</link>
      <guid>http://securityratty.com/article/81559287e233424259b25f0bd4b724e4</guid>
      <description><![CDATA[Steven J. Murdoch , Ross Anderson and I looked at how well PIN entry devices (PEDs) protect cardholder data. Our paper will be published at the IEEE Symposium on Security and Privacy in May, though an...]]></description>
      <content:encoded><![CDATA[<p><a href="http://www.cl.cam.ac.uk/~sjm217">Steven J. Murdoch</a>, <a href="http://www.cl.cam.ac.uk/~rja14">Ross Anderson</a> and I looked at how well PIN entry devices (PEDs) protect cardholder data. Our paper will be published at the <a href="http://www.ieee-security.org/TC/SP2008/oakland08.html">IEEE Symposium on Security and Privacy</a> in May, though an extended version is available as a <a href="http://www.cl.cam.ac.uk/techreports/UCAM-CL-TR-711.pdf">technical report</a>. A segment about this work will appear on BBC Two&#8217;s <a href="http://news.bbc.co.uk/1/hi/programmes/newsnight/default.stm">Newsnight</a> at 22:30 tonight.</p>
<p>We were able to demonstrate that two of the most popular PEDs in the UK &#8212; the Ingenico i3300 and Dione Xtreme &#8212; are vulnerable to a &#8220;tapping attack&#8221; using a paper clip, a needle and a small recording device. This allows us to record the data exchanged between the card and the PED&#8217;s processor without triggering tamper proofing mechanisms, and in clear violation of their supposed security properties. This attack can capture the card&#8217;s PIN because UK banks have opted to issue cheaper cards that do not use asymmetric cryptography to encrypt data between the card and PED.</p>
<p><a href="http://www.cl.cam.ac.uk/research/security/banking/ped/ingenico-tap.jpg"><img height="180" src="http://www.cl.cam.ac.uk/research/security/banking/ped/ingenico-tap.jpg" alt="Ingenico attack" /></a>&nbsp;<a href="http://www.cl.cam.ac.uk/research/security/banking/ped/dione-tap.jpg"><img height="180" src="http://www.cl.cam.ac.uk/research/security/banking/ped/dione-tap.jpg" alt="Dione attack" /></a></p>
<p>In addition to the PIN, as part of the transaction, the PED reads an exact replica of the magnetic strip (for backwards compatibility). Thus, if an attacker can tap the data line between the card and the PED&#8217;s processor, he gets all the information needed to create a magnetic strip card and withdraw money out of an ATM that does not read the chip.</p>
<p>We also found that the certification process of these PEDs is flawed. <a href="http://www.apacs.org.uk/">APACS</a> has been effectively approving PEDs for the UK market as Common Criteria (CC) <em><a href="http://www.apacs.org.uk/payment_options/PINEntryDevices.html">Evaluated</a></em>, which does not equal Common Criteria <em><a href="http://www.commoncriteriaportal.org/public/expert/index.php?menu=7">Certified</a></em> (no PEDs are CC Certified). What APACS means by &#8220;Evaluated&#8221; is that an approved lab has performed the &#8220;evaluation&#8221;, but unlike CC Certified products, the reports are kept secret, and governmental Certification Bodies do not do quality control.</p>
<p>This process causes a race to the bottom, with PED developers able to choose labs that will <em>approve</em> rather than <em>improve</em> PEDs, at the lowest price. Clearly, the certification process needs to be more open to the cardholders, who suffer from the fraud. It also needs to be fixed such that defective devices are refused certification.</p>
<p>We notified APACS, Visa, and the PED manufactures of our results in mid-November 2007 and responses arrived only in the last week or so (Visa chose to respond only a few minutes ago!) The <a href="http://www.cl.cam.ac.uk/research/security/banking/ped/#responses">responses</a> are the usual claims that our demonstrations can only be done in lab conditions, that criminals are not that sophisticated, the threat to cardholder data is minimal, and that their &#8220;layers of security&#8221; will detect fraud. There is no evidence to support these claims. APACS state that the PEDs we examined will not be de-certified or removed, and the same for the labs who certified them and would not even tell us who they are.</p>
<p>The threat is very real: tampered PEDs have already been used for fraud. See our <a href="http://www.cl.cam.ac.uk/research/security/banking/ped/press-release.html">press release</a> and <a href="http://www.cl.cam.ac.uk/research/security/banking/ped/">FAQ</a> for basic points and the <a href="http://www.cl.cam.ac.uk/techreports/UCAM-CL-TR-711.pdf">technical report</a> where we discuss the work in detail.</p>
]]></content:encoded>
      <pubDate>Tue, 26 Feb 2008 17:33:32 +0000</pubDate>
      <category domain="http://securityratty.com/tag/peds">peds</category>
      <category domain="http://securityratty.com/tag/popular peds">popular peds</category>
      <category domain="http://securityratty.com/tag/protect cardholder data">protect cardholder data</category>
      <category domain="http://securityratty.com/tag/peds processor">peds processor</category>
      <category domain="http://securityratty.com/tag/pin">pin</category>
      <category domain="http://securityratty.com/tag/cardholder data">cardholder data</category>
      <category domain="http://securityratty.com/tag/data">data</category>
      <category domain="http://securityratty.com/tag/encrypt data">encrypt data</category>
      <category domain="http://securityratty.com/tag/governmental certification bodies">governmental certification bodies</category>
      <source url="http://www.lightbluetouchpaper.org/2008/02/26/chip-pin-terminals-vulnerable-to-simple-attacks/">Chip &amp; PIN terminals vulnerable to simple attacks</source>
    </item>
  </channel>
</rss>
