Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Mon, 16 Dec 2013 20:35:37 +0100
From: Stefan B├╝hler <>
Subject: CVE request: Juvia secret token handling


Juvia is a Ruby on Rails application to host "comments":
> A commenting server similar to Disqus and IntenseDebate

It includes a "default" secret to validate cookies in 
`app/config/initializers/secret_token.rb', and the install instructions
do not include generating a new secret.
Also the file in question is maintained in git, and configuration
should not touch these files.

This means an attacker could modify session state, which is somehow
trusted by the Rails application.

A workaround for Juvia is to generate a new secret (`rake secret') and
replace the one in
`app/config/initializers/secret_token.rb' (invalidating all cookies,
don't forget to restart Juvia).
You have to be careful when switching between git branches and so on to
not loose the change.

The core problem is that rails generated the file that way; other gems
have similar issues.
The rails security team has been informed about this.

Kind regards,

* Juvia "public" secret:
* Juvia issue for this:

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)

Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.