J-Security Center

Latest Attack Object Updates
  • IDP Daily Update #1545
    posted: 11/19/09
  • NSM Daily Update #1545
    posted: 11/19/09
  • Deep Inspection 5.3r5 and above, 5.4, 6.0 #1545
    posted: 11/19/09
  • Deep Inspection 5.1 and 5.2 #1435
    posted: 11/19/09
  • Deep Inspection 5.0, 5.3r4 and below #1132
    posted: 03/28/08 (04/01/08 for 5.0)
  • Antivirus
    posted: 11/19/09

Title: tinc Weak Salt Length Traffic Pattern Analysis Vulnerability

Severity: MODERATE

Description:

tinc is a Virtual Private Network (VPN) daemon designed for Linux and Unix based systems. It acts as a tunnel for a network interface, and embeds all communication into a sequence of encrypted UDP packets. This allows private network communication to occur through a larger network. tinc uses blowfish in cipher block chaining (CBC) mode to encrypt packets. The secret key is shared via a PKI-style handshake during the authentication process between two tinc daemons.

In order to avoid the detection of regular traffic patterns (specifically, the ability to recognize repeated, identical packets), tinc prepends a two byte random salt to each packet before it is encrypted. While this is sufficient for many applications, under some circumstances traffic analysis may still be possible.

Due to the birthday paradox, the number of identical packets (excluding the random salt) that must be sent before a collision in salt values is likely is much less than the 65536 values possible. In fact, if approximately 2-300 identical packets are sent, a salt collision is over 50% probable.

This vulnerability is unlikely to affect most applications. For example, the TCP protocol includes a random sequence number, which may prevent a large number of completely identical packets from ever being transmitted. However, applications using a protocol such as UDP may be vulnerable.

Affected Products:

  • tinc tinc 1.0.0pre3
  • tinc tinc 1.0.0pre4

References:

Juniper Networks provides this content via a wide variety of sources and production methods. If notified of errors or omissions in the content of this page, Juniper Networks, at its discretion, will modify or remove the page or leave the content as is, depending on various factors including but not limited to the reputation and authority of the party providing the notification. Please use the contact information displayed elsewhere on this page to report any errors or omissions regarding the content on this page.