CVE-2009-0030: Medium severity Squirrelmail Squirrelmail vulnerability

Published Jan 17, 2009
·
Updated

A certain Red Hat patch for SquirrelMail 1.4.8 sets the same SQMSESSID cookie value for all sessions, which allows remote authenticated users to access other users' folder lists and configuration data in opportunistic circumstances by using the standard webmail.php interface. NOTE: this vulnerability exists because of an incorrect fix for CVE-2008-3663.

Other sources

It was discovered that a backport of the patch for CVE-2008-3663 included in SquirrelMail packages as shipped in Red Hat Enterprise Linux 3, 4, and 5 contained a bug, that could result in different users being assigned insecure and identical session identifier. Such session identifiers were assigned if user logged out of SquirrelMail and logged in again without closing web browser.

This could result in sessions of the multiple users to "merge". Certain data from one user's session could have been displayed to other user (such as folder structure, address book and options, but not individual mails), or result in the overwrite of the preferences data with other user's settings.

Further details can be found in the bug #480224.

Red Hat

Affected Software

1 affected component
Squirrelmail Squirrelmail=1.4.8

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    Advise or require users to fully close their web browser between logging out of SquirrelMail and logging in again. The vulnerability occurs when a user logs out and logs in again without closing the browser, which can result in identical SQMSESSID cookies and merged sessions; closing the browser between sessions prevents reuse of the same session identifier.

Event History

Jan 17, 2009
Data Sourced
via Red Hat·05:38 PM
DescriptionSeverityAffected Software
Jan 21, 2009
CVE Published
via MITRE·08:00 PM
Data Sourced
via MITRE·08:00 PM
Description
Data Sourced
via NVD·08:30 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2009-0030?

CVE-2009-0030 is classified as a medium severity vulnerability due to the potential for unauthorized access to user data.

2

How do I fix CVE-2009-0030?

To fix CVE-2009-0030, update SquirrelMail to a version that addresses this cookie management issue.

3

What software is affected by CVE-2009-0030?

CVE-2009-0030 specifically affects SquirrelMail version 1.4.8.

4

What type of vulnerability is CVE-2009-0030?

CVE-2009-0030 is a session management vulnerability that allows access to other users' session data.

5

Who can exploit CVE-2009-0030?

CVE-2009-0030 can be exploited by remote authenticated users who can manipulate the session cookie.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203