evolve or die

datakeyPassword.txt

datakeyPassword.txt
Posted Aug 5, 2004
Authored by HexView

Datakey's tokens and smartcards suffer from a clear text password exposure vulnerability. The communication channel between the token and the driver is not encrypted. A user's PIN can be retrieved using a proxy driver or hardware sniffer. Systems affected: Rainbow iKey2032 USB token and Datakey's up-to-date CIP client package.

tags | advisory
MD5 | eeb3ebb3e6ccc0a53b808eb6a13c65d2

datakeyPassword.txt

Change Mirror Download
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Clear text password exposure in Datakey's tokens and smartcards

Classification:
===============
Level: [LOW]-med-high-crit
ID: HEXVIEW*2004*08*03*1

Overview:
=========
Datakey (http://www.datakey.com) delivers smartcard and token-based
authentication and identity management solutions. Datakey's latest
smartcards and USB tokens are based on Philips 5032 cryptoprocessor
running DKCCOS (Datakey Cryptographic Card Operating System). An
implementation flaw makes possible to retrieve user's PIN by sniffing
communication channel between smartcard/token and smartcard driver.

Affected products:
==================
All tests were performed using Rainbow iKey2032 USB token and Datakey's
up-to-date CIP client package. Since the same firmware is also used in
Datakey's 330-series smartcards, all of them are also vulnerable.

Cause and Effect:
=================
The communication channel between the token and the driver is not
encrypted. User's PIN can be retrieved using proxy driver or hardware
sniffer. Retrieved password can later be used by attacker to authenticate
against the token and logon to the system, decrypt confidential
information, or perform other unauthorized activities depending on
what a specific smartcard implementation is used for.
Note that LOW risk level reflects overall industry impact. Since
Datakey's tokens and smartcards are used by many organizations to secure
critical information, the issue may be of much higher concern for some
users.

History Tour:
=============
The vulnerability described in this advisory is not the first and only
problem with Datakey's smartcards. There was an earlier (also resolved)
issue with smartcard driver caching user's PIN in clear text on a local
filesystem. It looks like Datakey may need to send its programmers to
attend some classes on how to write a secure code.

Vendor Status:
==============
Although HexView did not notify the vendor, Datakey was well aware of the
vulnerability and put significant efforts in order to address the issue.
As per reliable source of information, Datakey's new firmware version
encrypts communication channel utilizing Diffie-Hellman to exchange
encryption keys.

Please note that HexView does not notify vendors unless there is a prior
agreement to do so. Vendors interested in receiving notifications prior
to public disclosure or receiving more detailed analysis may obtain
more information by writing to the e-mail address provided at the end
of the document.

About HexView:
==============
HexView contributes to online security-related lists for almost a decade.
The scope of our expertize spreads over Windows, Linux, Sun, MacOS platforms,
network applications, and embedded devices. The chances are you read our
advisories or disclosures. For the sake of readability and easy web indexing
we recently decided to use the HexView alias to publish all the information.

Distribution:
=============
This document may be freely distributed through any channels as long as the
contents are kept unmodified. Commercial use of the information in the document
is not allowed without written permission from HexView signed by our pgp key.

Feedback and comments:
======================
Feedback and questions about this disclosure are welcome at vtalk@hexview.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBEG9pDPV1+KQrDqQRAjJzAKCTwJkfQmv9kKCmsgei7VZgaEHsagCcCwMl
/Hdru/H6y4HEmkFIHPbpOkU=
=p84D
-----END PGP SIGNATURE-----

Comments

RSS Feed Subscribe to this comment feed

No comments yet, be the first!

Login or Register to post a comment

File Archive:

May 2012

  • Su
  • Mo
  • Tu
  • We
  • Th
  • Fr
  • Sa
  • 1
    May 1st
    37 Files
  • 2
    May 2nd
    53 Files
  • 3
    May 3rd
    33 Files
  • 4
    May 4th
    4 Files
  • 5
    May 5th
    10 Files
  • 6
    May 6th
    17 Files
  • 7
    May 7th
    19 Files
  • 8
    May 8th
    36 Files
  • 9
    May 9th
    34 Files
  • 10
    May 10th
    35 Files
  • 11
    May 11th
    20 Files
  • 12
    May 12th
    18 Files
  • 13
    May 13th
    11 Files
  • 14
    May 14th
    27 Files
  • 15
    May 15th
    58 Files
  • 16
    May 16th
    54 Files
  • 17
    May 17th
    25 Files
  • 18
    May 18th
    53 Files
  • 19
    May 19th
    9 Files
  • 20
    May 20th
    15 Files
  • 21
    May 21st
    25 Files
  • 22
    May 22nd
    32 Files
  • 23
    May 23rd
    35 Files
  • 24
    May 24th
    26 Files
  • 25
    May 25th
    25 Files
  • 26
    May 26th
    0 Files
  • 27
    May 27th
    0 Files
  • 28
    May 28th
    0 Files
  • 29
    May 29th
    0 Files
  • 30
    May 30th
    0 Files
  • 31
    May 31st
    0 Files

Top Authors In Last 30 Days

File Tags

Systems

packet storm

© 2012 Packet Storm. All rights reserved.

close