Drupal CMS fails to set the secure flag in the session cookie allowing for session hijacking.
6d5d4657228cd6039e3ccbfbac2cd8adc8cdb25a11f076f03f379e89ca0016db
drupal: Session hijacking vulnerability, CVE-2008-3661
References
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-3661
http://int21.de/cve/CVE-2008-3661-drupal.html
http://enablesecurity.com/2008/08/11/surf-jack-https-will-not-save-you/
https://www.defcon.org/html/defcon-16/dc-16-speakers.html#Perry
Description
When configuring a web application to use only ssl (e. g. by forwarding all
http-requests to https), a user would expect that sniffing and hijacking the
session is impossible.
Though, for this to be secure, one needs to set the session cookie to have the
secure flag. Else the cookie will be transferred through http if the victim's
browser does a single http-request on the same domain.
The drupal CMS is vulnerable to this issue. They don't consider this as a
drupal issue and have not published a fix yet.
Disclosure Timeline
2008-08-13: Vendor contacted
2008-09-20 Published advisory
Credits and copyright
This vulnerability was discovered by Hanno Boeck of schokokeks.org webhosting.
It's licensed under the creative commons attribution license.
Hanno Boeck, http://www.hboeck.de
--
Hanno Böck Blog: http://www.hboeck.de/
GPG: 3DBD3B20 Jabber/Mail: hanno@hboeck.de