Slash-based bulletin boards contain a "quick login" feature that may disclose username and password

ID VU:603945
Type cert
Reporter CERT
Modified 2003-02-06T00:00:00



Slash-based bulletin boards contain a vulnerability that may cause users to disclose their username and password to third-party sites.


As described in the Slashcode FAQ, "Slash is a database-driven news and message board, using Perl, Apache and MySQL." Slash allows web site maintainers to create a custom bulletin board site using the same technology as the popular website Slashdot.

Slash-based bulletin boards provide a "quick login" feature that allows users to bookmark a pre-formatted URL containing their account username and password. For users who are either unable or unwilling to store their session information in a cookie, this feature allows logins without the need to type a username and password. However, because the authentication information is contained within the URL, it may be disclosed to other sites. In particular, when users visit a link from the bulletin board to an external site, their login information may be passed via the HTTP Referer header.


This vulnerability causes bulletin board account information to be disclosed in HTTP GET requests and Referer headers.


The CERT/CC is currently unaware of a practical solution to this problem.

Use session cookies

Slash provides users with the option to maintain a persistent login session by storing authentication information within their web browsers. Using this option in lieu of the "quick login" feature will prevent username and password information from being disclosed in HTTP Referer headers.

Systems Affected

Vendor| Status| Date Notified| Date Updated
---|---|---|---| | 12 Sep 2002| 12 Sep 2002
If you are a vendor and your product is affected, let us know.

CVSS Metrics

Group | Score | Vector
Base | N/A | N/A
Temporal | N/A | N/A
Environmental | N/A | N/A


  • <>


This vulnerability was reported to the Bugtraq mailing list by Michal Zalewski.

This document was written by Jeffrey P. Lanza.

Other Information

  • CVE IDs: Unknown
  • Date Public: 11 Sep 2002
  • Date First Published: 31 Jan 2003
  • Date Last Updated: 06 Feb 2003
  • Severity Metric: 1.35
  • Document Revision: 12