Vulnerability Note VU#581068

NotifyLink server provides inadequate protection for cryptographic key material

Overview

The NotifyLink key exchange protocol contains a vulnerability that significantly reduces the strength of cryptographic keys used to encrypt mail messages.

I. Description

Notify Technology NotifyLink Enterprise Server allows users to synchronize e-mail between a PDA and a mail server. The application consists of a PDA-specific client and the NotifyLink server, which acts as a proxy between the client and the mail server(s) the user wants to check. For each e-mail account to be monitored, the user provides mail server credentials that are stored on the NotifyLink server and used to periodically check for mail. When new mail arrives, the NotifyLink server stores a reference to the message ID. Depending on the configuration, the message is either sent to the device via SMS ("Push" mode), or the device periodically checks a link on the NotifyLink web server to retrieve the message ("Poll" mode). The product supports multiple PDA platforms and multiple e-mail servers, including IMAP, POP, Microsoft Exchange, and Novell GroupWise.

NotifyLink uses AES keys to encrypt the mail messages that are exchanged between the PDA and NotifyLink server. These keys are stored on the server in a table named ClientDevices, which is protected from unauthenticated access. If the key is not transferred to the PDA manually, the client can retrieve it from the server using an unauthenticated HTTP post to /hwp/get.asp. When keys are transmitted using this method, the server uses a fixed byte reordering scheme to obfuscate the key. This scheme significantly reduces the strength of the key material, providing protection against only the most casual observer. In addition, any attacker in possession of the source code for get.asp will be able to determine the fixed scheme, making the reversal operation trivial.

II. Impact

This vulnerability significantly reduces the strength of cryptographic keys used to encrypt mail messages.

III. Solution

Use Manual Key Generation

Configure NotifyLink to use "Manual Key Generation." When NotifyLink is configured this way, the obfuscated key will not be available to an attacker via /hwp/get.asp.

Systems Affected

Vendor	Status	Date Notified	Date Updated
Notify Technology	Vulnerable	3-May-2004

References

http://notifylink.notify.net
http://secunia.com/advisories/14617/
http://www.securityfocus.com/bid/12843

Credit

We thank the NOAA NCIRT Lab for their discovery and analysis of this vulnerability.

This document was written by Jeffrey P Lanza and Will Dormann. It is based on analysis provided by the NOAA NCIRT Lab.

Other Information

Date Public:	2005-03-17
Date First Published:	2005-03-17
Date Last Updated:	2005-04-28
CERT Advisory:
CVE-ID(s):	CAN-2005-0809
NVD-ID(s):	CAN-2005-0809
US-CERT Technical Alerts:
Metric:	0.00
Document Revision:	32

If you have feedback, comments, or additional information about this vulnerability, please send us email.

Get Adobe Reader