CVE-2008-3661
First published: Tue Sep 23 2008(Updated: )
Drupal, probably 5.10 and 6.4, does not set the secure flag for the session cookie in an https session, which can cause the cookie to be sent in http requests and make it easier for remote attackers to capture this cookie.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Drupal Drupal | =5.10 | |
| Drupal Drupal | =6.4 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2008-3661?
CVE-2008-3661 is considered a medium severity vulnerability due to the risk of session cookies being exposed to attackers.
How do I fix CVE-2008-3661?
To fix CVE-2008-3661, ensure that the secure flag is set for session cookies in your Drupal configuration during HTTPS sessions.
Which versions of Drupal are affected by CVE-2008-3661?
CVE-2008-3661 affects Drupal versions 5.10 and 6.4.
What is the impact of CVE-2008-3661?
The impact of CVE-2008-3661 allows attackers to potentially capture session cookies, leading to unauthorized access.
Is there a patch available for CVE-2008-3661?
Yes, upgrading to newer versions of Drupal that properly set the secure flag for session cookies will mitigate CVE-2008-3661.
- collector/nvd-historical
- collector/nvd-index
- agent/references
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/weakness
- agent/last-modified-date
- agent/author
- agent/description
- agent/tags
- agent/event
- agent/first-publish-date
- agent/source
- vendor/drupal
- canonical/drupal drupal
- version/drupal drupal/5.10
- version/drupal drupal/6.4