|
CGI::Session Insecure Default Session File Permissions
|
|
Secunia Advisory:
|
SA19211
|
|
|
Release Date:
|
2006-03-13
|
|
Last Update:
|
2006-03-22
|
|
Popularity:
|
5,399 views
|
|
|
Critical:
|
Less critical
|
|
Impact:
|
Exposure of sensitive information
|
|
Where:
|
From remote
|
|
Solution Status:
|
Vendor Patch
|
|
| Software: | CGI::Session 4.x
|
|
|
Secunia CVSS-2 Score:
|
Available in Secunia business solutions 
|
|
|
Subscribe:
|
Instant alerts on relevant vulnerabilities
|
|
| Advisory Content (Page 1 of 3) | [ 1 ] [ 2 ] [ 3 ] | |
|
Description:
Joey Hess has reported some security issues in CGI::Session, which potentially can be exploited by malicious, local users and by malicious people to disclose certain sensitive information.
1) Session files are created by Driver::file, Driver::db_file, and Driver::sqlite with insecure default read permissions. This can potentially be exploited by malicious, local users to gain knowledge of data stored in session files, e.g. Driver::file stores the session files in "/tmp" by default.
2) The "cgisess.db" session file is created by Driver::db_file in the same directory as the CGI script. In certain configurations, this file may be created in a web accessible directory. This can potentially be exploited by malicious people to gain knowledge of session data.
The security issues have been reported in version 4.03. Other versions may also be affected.
Change Page:
[ 1 ] [ 2 ] [ 3 ]
|
|
|
Track this Secunia Advisory
|
Customers of the Secunia Vulnerability Intelligence solutions will automatically receive updates when new information regarding this advisory is released.
Read more about our Vulnerability Intelligence solutions and what they can do for you and your company.
|
|
|
About this Secunia Advisory
|
Please note: The information that this Secunia Advisory is based on comes from a third party unless stated otherwise.
Secunia collects, validates, and verifies all vulnerability reports issued by security research groups, vendors, and others.
|
