Insecure secure cookie in Tornado

English | Vietnamese

Rules

Main Forum

Portal

Member Listing

Statistics

Search

Reading Room
[Register]

Login [ | https ]

Forum Index

Thông tin new bugs và exploits

Insecure secure cookie in Tornado

[Announcement] Insecure secure cookie in Tornado	16/08/2010 10:19:46 (+0700) \| #1 \| 218484

bmrobot
Member

Joined: 21/08/2008 17:43:51
Messages: 11
Offline

BLUE MOON SECURITY ADVISORY 2010-01
===================================

:Title: Insecure secure cookie in Tornado
:Severity: Low
:Reporter: Blue Moon Consulting
:Products: Tornado v1.0
:Fixed in: Tornado v1.0.1

Description
-----------

Tornado is an open source version of the scalable, non-blocking web server and tools that power FriendFeed.

A secure cookie in Tornado is stored in three parts, separated by a pipe sign (``|``)

::

<value>|<timestamp>|<hmac>

where:

<value>
is the cookie's value encoded in Base64, which does use the digits 0 to 9.

<timestamp>
is ``str(int(time.time()))``.

<hmac>
is the keyed hash value of <value> and <timestamp> concatenated.

The problem is ``get_secure_cookie`` only checks for expired timestamp and the <hmac> does not take into account the separator character. An attacker, therefore, can move the pipe sign to the left by 4-character blocks to create another valid cookie, whose timestamp is in the far future, and value truncated by 3 characters.

This vulnerability is rated at low severity due to situational exploiting conditions.

Workaround
----------

There is no workaround.

Fix
---

Customers are advised to upgrade to at least version 1.0.1.

Disclosure
----------

Blue Moon Consulting adapts `RFPolicy v2.0 <http://www.wiretrip.net/rfp/policy.html>`_ in notifying vendors.

:Initial vendor contact:

August 13, 2010: Notice sent to Ben Darnell.

:Vendor response:

August 13, 2010: Ben replied confirming the bug.

:Further communication:

August 13, 2010: Ben added that the attacker would have to shift by 4 digits due to Base64 encoding.

August 13, 2010: Ben added that version 1.0.1 would have a timestamp check.

:Public disclosure: August 16, 2010

:Exploit code:

No exploit code required.

Disclaimer
----------

The information provided in this advisory is provided "as is" without warranty of any kind. Blue Moon Consulting Co., Ltd disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Your use of the information on the advisory or materials linked from the advisory is at your own risk. Blue Moon Consulting Co., Ltd reserves the right to change or update this notice at any time.

Go to:

Users currently in here
1 Anonymous