ID CVE-2009-1580
Summary Session fixation vulnerability in SquirrelMail before 1.4.18 allows remote attackers to hijack web sessions via a crafted cookie.
References
Vulnerable Configurations
  • cpe:2.3:a:squirrelmail:squirrelmail:0.1
    cpe:2.3:a:squirrelmail:squirrelmail:0.1
  • cpe:2.3:a:squirrelmail:squirrelmail:0.1.1
    cpe:2.3:a:squirrelmail:squirrelmail:0.1.1
  • cpe:2.3:a:squirrelmail:squirrelmail:0.1.2
    cpe:2.3:a:squirrelmail:squirrelmail:0.1.2
  • cpe:2.3:a:squirrelmail:squirrelmail:0.2
    cpe:2.3:a:squirrelmail:squirrelmail:0.2
  • cpe:2.3:a:squirrelmail:squirrelmail:0.2.1
    cpe:2.3:a:squirrelmail:squirrelmail:0.2.1
  • cpe:2.3:a:squirrelmail:squirrelmail:0.3
    cpe:2.3:a:squirrelmail:squirrelmail:0.3
  • cpe:2.3:a:squirrelmail:squirrelmail:0.3.1
    cpe:2.3:a:squirrelmail:squirrelmail:0.3.1
  • cpe:2.3:a:squirrelmail:squirrelmail:0.4
    cpe:2.3:a:squirrelmail:squirrelmail:0.4
  • cpe:2.3:a:squirrelmail:squirrelmail:0.5
    cpe:2.3:a:squirrelmail:squirrelmail:0.5
  • cpe:2.3:a:squirrelmail:squirrelmail:1.0
    cpe:2.3:a:squirrelmail:squirrelmail:1.0
  • cpe:2.3:a:squirrelmail:squirrelmail:1.0.1
    cpe:2.3:a:squirrelmail:squirrelmail:1.0.1
  • cpe:2.3:a:squirrelmail:squirrelmail:1.0.2
    cpe:2.3:a:squirrelmail:squirrelmail:1.0.2
  • cpe:2.3:a:squirrelmail:squirrelmail:1.0.3
    cpe:2.3:a:squirrelmail:squirrelmail:1.0.3
  • cpe:2.3:a:squirrelmail:squirrelmail:1.0.4
    cpe:2.3:a:squirrelmail:squirrelmail:1.0.4
  • cpe:2.3:a:squirrelmail:squirrelmail:1.0.5
    cpe:2.3:a:squirrelmail:squirrelmail:1.0.5
  • cpe:2.3:a:squirrelmail:squirrelmail:1.0.6
    cpe:2.3:a:squirrelmail:squirrelmail:1.0.6
  • cpe:2.3:a:squirrelmail:squirrelmail:1.1.0
    cpe:2.3:a:squirrelmail:squirrelmail:1.1.0
  • cpe:2.3:a:squirrelmail:squirrelmail:1.1.2
    cpe:2.3:a:squirrelmail:squirrelmail:1.1.2
  • cpe:2.3:a:squirrelmail:squirrelmail:1.1.3
    cpe:2.3:a:squirrelmail:squirrelmail:1.1.3
  • cpe:2.3:a:squirrelmail:squirrelmail:1.2
    cpe:2.3:a:squirrelmail:squirrelmail:1.2
  • cpe:2.3:a:squirrelmail:squirrelmail:1.2.0
    cpe:2.3:a:squirrelmail:squirrelmail:1.2.0
  • cpe:2.3:a:squirrelmail:squirrelmail:1.2.0:rc3
    cpe:2.3:a:squirrelmail:squirrelmail:1.2.0:rc3
  • cpe:2.3:a:squirrelmail:squirrelmail:1.2.1
    cpe:2.3:a:squirrelmail:squirrelmail:1.2.1
  • cpe:2.3:a:squirrelmail:squirrelmail:1.2.10
    cpe:2.3:a:squirrelmail:squirrelmail:1.2.10
  • cpe:2.3:a:squirrelmail:squirrelmail:1.2.11
    cpe:2.3:a:squirrelmail:squirrelmail:1.2.11
  • cpe:2.3:a:squirrelmail:squirrelmail:1.2.2
    cpe:2.3:a:squirrelmail:squirrelmail:1.2.2
  • cpe:2.3:a:squirrelmail:squirrelmail:1.2.3
    cpe:2.3:a:squirrelmail:squirrelmail:1.2.3
  • cpe:2.3:a:squirrelmail:squirrelmail:1.2.4
    cpe:2.3:a:squirrelmail:squirrelmail:1.2.4
  • cpe:2.3:a:squirrelmail:squirrelmail:1.2.5
    cpe:2.3:a:squirrelmail:squirrelmail:1.2.5
  • cpe:2.3:a:squirrelmail:squirrelmail:1.2.6
    cpe:2.3:a:squirrelmail:squirrelmail:1.2.6
  • cpe:2.3:a:squirrelmail:squirrelmail:1.2.7
    cpe:2.3:a:squirrelmail:squirrelmail:1.2.7
  • cpe:2.3:a:squirrelmail:squirrelmail:1.2.8
    cpe:2.3:a:squirrelmail:squirrelmail:1.2.8
  • cpe:2.3:a:squirrelmail:squirrelmail:1.2.9
    cpe:2.3:a:squirrelmail:squirrelmail:1.2.9
  • cpe:2.3:a:squirrelmail:squirrelmail:1.3.0
    cpe:2.3:a:squirrelmail:squirrelmail:1.3.0
  • cpe:2.3:a:squirrelmail:squirrelmail:1.4
    cpe:2.3:a:squirrelmail:squirrelmail:1.4
  • cpe:2.3:a:squirrelmail:squirrelmail:1.4.0
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.0
  • cpe:2.3:a:squirrelmail:squirrelmail:1.4.0:rc1
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.0:rc1
  • cpe:2.3:a:squirrelmail:squirrelmail:1.4.0:rc2a
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.0:rc2a
  • cpe:2.3:a:squirrelmail:squirrelmail:1.4.1
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.1
  • cpe:2.3:a:squirrelmail:squirrelmail:1.4.10a
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.10a
  • cpe:2.3:a:squirrelmail:squirrelmail:1.4.11
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.11
  • cpe:2.3:a:squirrelmail:squirrelmail:1.4.12
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.12
  • cpe:2.3:a:squirrelmail:squirrelmail:1.4.15
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.15
  • cpe:2.3:a:squirrelmail:squirrelmail:1.4.15:rc1
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.15:rc1
  • cpe:2.3:a:squirrelmail:squirrelmail:1.4.16
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.16
  • cpe:2.3:a:squirrelmail:squirrelmail:1.4.17
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.17
  • cpe:2.3:a:squirrelmail:squirrelmail:1.4.2
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.2
  • cpe:2.3:a:squirrelmail:squirrelmail:1.4.3
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.3
  • cpe:2.3:a:squirrelmail:squirrelmail:1.4.3:r3
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.3:r3
  • cpe:2.3:a:squirrelmail:squirrelmail:1.4.3:rc1
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.3:rc1
  • cpe:2.3:a:squirrelmail:squirrelmail:1.4.3a
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.3a
  • cpe:2.3:a:squirrelmail:squirrelmail:1.4.3aa
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.3aa
  • cpe:2.3:a:squirrelmail:squirrelmail:1.4.4
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.4
  • cpe:2.3:a:squirrelmail:squirrelmail:1.4.4:rc1
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.4:rc1
  • cpe:2.3:a:squirrelmail:squirrelmail:1.4.5
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.5
  • cpe:2.3:a:squirrelmail:squirrelmail:1.4.6
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.6
  • cpe:2.3:a:squirrelmail:squirrelmail:1.4.6:rc1
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.6:rc1
  • cpe:2.3:a:squirrelmail:squirrelmail:1.4.7
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.7
  • cpe:2.3:a:squirrelmail:squirrelmail:1.4.8.4fc6
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.8.4fc6
  • cpe:2.3:a:squirrelmail:squirrelmail:1.4.9
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.9
  • cpe:2.3:a:squirrelmail:squirrelmail:1.4.9a
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.9a
  • cpe:2.3:a:squirrelmail:squirrelmail:1.4:rc1
    cpe:2.3:a:squirrelmail:squirrelmail:1.4:rc1
  • cpe:2.3:a:squirrelmail:squirrelmail:1.44
    cpe:2.3:a:squirrelmail:squirrelmail:1.44
  • cpe:2.3:a:squirrelmail:squirrelmail:1.0pre3
    cpe:2.3:a:squirrelmail:squirrelmail:1.0pre3
  • cpe:2.3:a:squirrelmail:squirrelmail:1.0pre2
    cpe:2.3:a:squirrelmail:squirrelmail:1.0pre2
  • cpe:2.3:a:squirrelmail:squirrelmail:1.0pre1
    cpe:2.3:a:squirrelmail:squirrelmail:1.0pre1
  • cpe:2.3:a:squirrelmail:squirrelmail:0.5pre2
    cpe:2.3:a:squirrelmail:squirrelmail:0.5pre2
  • cpe:2.3:a:squirrelmail:squirrelmail:0.5pre1
    cpe:2.3:a:squirrelmail:squirrelmail:0.5pre1
  • cpe:2.3:a:squirrelmail:squirrelmail:0.4pre2
    cpe:2.3:a:squirrelmail:squirrelmail:0.4pre2
  • cpe:2.3:a:squirrelmail:squirrelmail:0.4pre1
    cpe:2.3:a:squirrelmail:squirrelmail:0.4pre1
  • cpe:2.3:a:squirrelmail:squirrelmail:0.3pre1
    cpe:2.3:a:squirrelmail:squirrelmail:0.3pre1
  • cpe:2.3:a:squirrelmail:squirrelmail:0.3pre2
    cpe:2.3:a:squirrelmail:squirrelmail:0.3pre2
CVSS
Base: 5.8 (as of 15-05-2009 - 10:47)
Impact:
Exploitability:
CWE CWE-287
CAPEC
  • Authentication Abuse
    An attacker obtains unauthorized access to an application, service or device either through knowledge of the inherent weaknesses of an authentication mechanism, or by exploiting a flaw in the authentication scheme's implementation. In such an attack an authentication mechanism is functioning but a carefully controlled sequence of events causes the mechanism to grant access to the attacker. This attack may exploit assumptions made by the target's authentication procedures, such as assumptions regarding trust relationships or assumptions regarding the generation of secret values. This attack differs from Authentication Bypass attacks in that Authentication Abuse allows the attacker to be certified as a valid user through illegitimate means, while Authentication Bypass allows the user to access protected material without ever being certified as an authenticated user. This attack does not rely on prior sessions established by successfully authenticating users, as relied upon for the "Exploitation of Session Variables, Resource IDs and other Trusted Credentials" attack patterns.
  • Exploiting Trust in Client (aka Make the Client Invisible)
    An attack of this type exploits a programs' vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client. An attacker executes this type of attack by placing themselves in the communication channel between client and server such that communication directly to the server is possible where the server believes it is communicating only with a valid client. There are numerous variations of this type of attack.
  • Utilizing REST's Trust in the System Resource to Register Man in the Middle
    This attack utilizes a REST(REpresentational State Transfer)-style applications' trust in the system resources and environment to place man in the middle once SSL is terminated. Rest applications premise is that they leverage existing infrastructure to deliver web services functionality. An example of this is a Rest application that uses HTTP Get methods and receives a HTTP response with an XML document. These Rest style web services are deployed on existing infrastructure such as Apache and IIS web servers with no SOAP stack required. Unfortunately from a security standpoint, there frequently is no interoperable identity security mechanism deployed, so Rest developers often fall back to SSL to deliver security. In large data centers, SSL is typically terminated at the edge of the network - at the firewall, load balancer, or router. Once the SSL is terminated the HTTP request is in the clear (unless developers have hashed or encrypted the values, but this is rare). The attacker can utilize a sniffer such as Wireshark to snapshot the credentials, such as username and password that are passed in the clear once SSL is terminated. Once the attacker gathers these credentials, they can submit requests to the web service provider just as authorized user do. There is not typically an authentication on the client side, beyond what is passed in the request itself so once this is compromised, then this is generally sufficient to compromise the service's authentication scheme.
  • Man in the Middle Attack
    This type of attack targets the communication between two components (typically client and server). The attacker places himself in the communication channel between the two components. Whenever one component attempts to communicate with the other (data flow, authentication challenges, etc.), the data first goes to the attacker, who has the opportunity to observe or alter it, and it is then passed on to the other component as if it was never intercepted. This interposition is transparent leaving the two compromised components unaware of the potential corruption or leakage of their communications. The potential for Man-in-the-Middle attacks yields an implicit lack of trust in communication or identify between two components.
Access
VectorComplexityAuthentication
NETWORK MEDIUM NONE
Impact
ConfidentialityIntegrityAvailability
PARTIAL PARTIAL NONE
nessus via4
  • NASL family MacOS X Local Security Checks
    NASL id MACOSX_SECUPD2010-004.NASL
    description The remote host is running a version of Mac OS X 10.5 that does not have Security Update 2010-004 applied. This security update contains fixes for the following components : - CUPS - DesktopServices - Flash Player plug-in - Folder Manager - iChat - ImageIO - Kerberos - Kernel - libcurl - Network Authorization - Ruby - SMB File Server - SquirrelMail - Wiki Server
    last seen 2019-02-21
    modified 2018-07-14
    plugin id 47024
    published 2010-06-15
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=47024
    title Mac OS X Multiple Vulnerabilities (Security Update 2010-004)
  • NASL family Debian Local Security Checks
    NASL id DEBIAN_DSA-1802.NASL
    description Several remote vulnerabilities have been discovered in SquirrelMail, a webmail application. The Common Vulnerabilities and Exposures project identifies the following problems : - CVE-2009-1578 Cross site scripting was possible through a number of pages which allowed an attacker to steal sensitive session data. - CVE-2009-1579, CVE-2009-1381 Code injection was possible when SquirrelMail was configured to use the map_yp_alias function to authenticate users. This is not the default. - CVE-2009-1580 It was possible to hijack an active user session by planting a specially crafted cookie into the user's browser. - CVE-2009-1581 Specially crafted HTML emails could use the CSS positioning feature to place email content over the SquirrelMail user interface, allowing for phishing.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 38859
    published 2009-05-20
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=38859
    title Debian DSA-1802-2 : squirrelmail - several vulnerabilities
  • NASL family Red Hat Local Security Checks
    NASL id REDHAT-RHSA-2009-0057.NASL
    description An updated squirrelmail package that fixes a security issue is now available for Red Hat Enterprise Linux 3, 4 and 5. This update has been rated as having important security impact by the Red Hat Security Response Team. SquirrelMail is an easy-to-configure, standards-based, webmail package written in PHP. It includes built-in PHP support for the IMAP and SMTP protocols, and pure HTML 4.0 page-rendering (with no JavaScript required) for maximum browser-compatibility, strong MIME support, address books, and folder manipulation. The Red Hat SquirrelMail packages provided by the RHSA-2009:0010 advisory introduced a session handling flaw. Users who logged back into SquirrelMail without restarting their web browsers were assigned fixed session identifiers. A remote attacker could make use of that flaw to hijack user sessions. (CVE-2009-0030) SquirrelMail users should upgrade to this updated package, which contains a patch to correct this issue. As well, all users who used affected versions of SquirrelMail should review their preferences.
    last seen 2019-02-21
    modified 2018-11-27
    plugin id 35429
    published 2009-01-20
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=35429
    title RHEL 3 / 4 / 5 : squirrelmail (RHSA-2009:0057)
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2009-4880.NASL
    description squirrelmail is now able to work with unsigned 32bit UID values with 32-bit version of php Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2016-12-08
    plugin id 38750
    published 2009-05-13
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=38750
    title Fedora 10 : squirrelmail-1.4.18-1.fc10 (2009-4880)
  • NASL family Gentoo Local Security Checks
    NASL id GENTOO_GLSA-201001-08.NASL
    description The remote host is affected by the vulnerability described in GLSA-201001-08 (SquirrelMail: Multiple vulnerabilities) Multiple vulnerabilities were found in SquirrelMail: Niels Teusink reported multiple input sanitation flaws in certain encrypted strings in e-mail headers, related to contrib/decrypt_headers.php, PHP_SELF and the query string (aka QUERY_STRING) (CVE-2009-1578). Niels Teusink also reported that the map_yp_alias() function in functions/imap_general.php does not filter shell metacharacters in a username and that the original patch was incomplete (CVE-2009-1381, CVE-2009-1579). Tomas Hoger discovered an unspecified session fixation vulnerability (CVE-2009-1580). Luc Beurton reported that functions/mime.php does not protect the application's content from Cascading Style Sheets (CSS) positioning in HTML e-mail messages (CVE-2009-1581). Impact : The vulnerabilities allow remote attackers to execute arbitrary code with the privileges of the user running the web server, to hijack web sessions via a crafted cookie, to spoof the user interface and to conduct Cross-Site Scripting and phishing attacks, via a specially crafted message. Workaround : There is no known workaround at this time.
    last seen 2019-02-21
    modified 2018-08-10
    plugin id 44897
    published 2010-02-25
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=44897
    title GLSA-201001-08 : SquirrelMail: Multiple vulnerabilities
  • NASL family CentOS Local Security Checks
    NASL id CENTOS_RHSA-2009-0057.NASL
    description An updated squirrelmail package that fixes a security issue is now available for Red Hat Enterprise Linux 3, 4 and 5. This update has been rated as having important security impact by the Red Hat Security Response Team. SquirrelMail is an easy-to-configure, standards-based, webmail package written in PHP. It includes built-in PHP support for the IMAP and SMTP protocols, and pure HTML 4.0 page-rendering (with no JavaScript required) for maximum browser-compatibility, strong MIME support, address books, and folder manipulation. The Red Hat SquirrelMail packages provided by the RHSA-2009:0010 advisory introduced a session handling flaw. Users who logged back into SquirrelMail without restarting their web browsers were assigned fixed session identifiers. A remote attacker could make use of that flaw to hijack user sessions. (CVE-2009-0030) SquirrelMail users should upgrade to this updated package, which contains a patch to correct this issue. As well, all users who used affected versions of SquirrelMail should review their preferences.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 35424
    published 2009-01-20
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=35424
    title CentOS 3 / 4 / 5 : squirrelmail (CESA-2009:0057)
  • NASL family MacOS X Local Security Checks
    NASL id MACOSX_10_6_4.NASL
    description The remote host is running a version of Mac OS X 10.6.x that is prior to 10.6.4. Mac OS X 10.6.4 contains security fixes for the following components : - CUPS - DesktopServices - Flash Player plug-in - Folder Manager - Help Viewer - iChat - ImageIO - Kerberos - Kernel - libcurl - Network Authorization - Open Directory - Printer Setup - Printing - Ruby - SMB File Server - SquirrelMail - Wiki Server
    last seen 2019-02-21
    modified 2018-07-14
    plugin id 47023
    published 2010-06-15
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=47023
    title Mac OS X 10.6.x < 10.6.4 Multiple Vulnerabilities
  • NASL family Oracle Linux Local Security Checks
    NASL id ORACLELINUX_ELSA-2009-0057.NASL
    description From Red Hat Security Advisory 2009:0057 : An updated squirrelmail package that fixes a security issue is now available for Red Hat Enterprise Linux 3, 4 and 5. This update has been rated as having important security impact by the Red Hat Security Response Team. SquirrelMail is an easy-to-configure, standards-based, webmail package written in PHP. It includes built-in PHP support for the IMAP and SMTP protocols, and pure HTML 4.0 page-rendering (with no JavaScript required) for maximum browser-compatibility, strong MIME support, address books, and folder manipulation. The Red Hat SquirrelMail packages provided by the RHSA-2009:0010 advisory introduced a session handling flaw. Users who logged back into SquirrelMail without restarting their web browsers were assigned fixed session identifiers. A remote attacker could make use of that flaw to hijack user sessions. (CVE-2009-0030) SquirrelMail users should upgrade to this updated package, which contains a patch to correct this issue. As well, all users who used affected versions of SquirrelMail should review their preferences.
    last seen 2019-02-21
    modified 2018-08-13
    plugin id 67794
    published 2013-07-12
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=67794
    title Oracle Linux 3 / 4 / 5 : squirrelmail (ELSA-2009-0057)
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2009-4875.NASL
    description - Tue May 12 2009 Michal Hlavinka - 1.4.18-1 - updated to 1.4.18 Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2016-12-08
    plugin id 38749
    published 2009-05-13
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=38749
    title Fedora 11 : squirrelmail-1.4.18-1.fc11 (2009-4875)
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2009-4870.NASL
    description - Tue May 12 2009 Michal Hlavinka - 1.4.18-1 - update to 1.4.18 (fixes CVE-2009-1581) - Thu Dec 4 2008 Michal Hlavinka - 1.4.17-1 - update to 1.4.17 (fixes CVE-2008-2379) - Wed Oct 1 2008 Michal Hlavinka - 1.4.16-1 - update to 1.4.16 - resolves: #464185: CVE-2008-3663 Squirrelmail session hijacking Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2016-12-08
    plugin id 38748
    published 2009-05-13
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=38748
    title Fedora 9 : squirrelmail-1.4.18-1.fc9 (2009-4870)
  • NASL family SuSE Local Security Checks
    NASL id SUSE_SQUIRRELMAIL-6242.NASL
    description Multiple vulnerabilities have been fixed in SquirrelMail: an XSS and input sanitization bug (both CVE-2009-1578), a server-side code execution (CVE-2009-1579), a login session hijacking bug (CVE-2009-1580) and another bug that allowed phishing and XSS attacks (CVE-2009-1581).
    last seen 2019-02-21
    modified 2016-12-27
    plugin id 38776
    published 2009-05-14
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=38776
    title openSUSE 10 Security Update : squirrelmail (squirrelmail-6242)
oval via4
accepted 2013-04-29T04:01:43.268-04:00
class vulnerability
contributors
  • name Aharon Chernin
    organization SCAP.com, LLC
  • name Dragos Prisaca
    organization G2, Inc.
definition_extensions
  • comment The operating system installed on the system is Red Hat Enterprise Linux 3
    oval oval:org.mitre.oval:def:11782
  • comment CentOS Linux 3.x
    oval oval:org.mitre.oval:def:16651
  • comment The operating system installed on the system is Red Hat Enterprise Linux 4
    oval oval:org.mitre.oval:def:11831
  • comment CentOS Linux 4.x
    oval oval:org.mitre.oval:def:16636
  • comment Oracle Linux 4.x
    oval oval:org.mitre.oval:def:15990
  • comment The operating system installed on the system is Red Hat Enterprise Linux 5
    oval oval:org.mitre.oval:def:11414
  • comment The operating system installed on the system is CentOS Linux 5.x
    oval oval:org.mitre.oval:def:15802
  • comment Oracle Linux 5.x
    oval oval:org.mitre.oval:def:15459
description Session fixation vulnerability in SquirrelMail before 1.4.18 allows remote attackers to hijack web sessions via a crafted cookie.
family unix
id oval:org.mitre.oval:def:10107
status accepted
submitted 2010-07-09T03:56:16-04:00
title Session fixation vulnerability in SquirrelMail before 1.4.18 allows remote attackers to hijack web sessions via a crafted cookie.
version 24
redhat via4
advisories
bugzilla
id 480488
title CVE-2009-0030 squirrelmail: session management flaw
oval
OR
  • AND
    • comment Red Hat Enterprise Linux 3 is installed
      oval oval:com.redhat.rhsa:tst:20060015001
    • comment squirrelmail is earlier than 0:1.4.8-9.el3
      oval oval:com.redhat.rhsa:tst:20090057002
    • comment squirrelmail is signed with Red Hat master key
      oval oval:com.redhat.rhsa:tst:20070022003
  • AND
    • comment Red Hat Enterprise Linux 4 is installed
      oval oval:com.redhat.rhsa:tst:20060016001
    • comment squirrelmail is earlier than 0:1.4.8-5.el4_7.3
      oval oval:com.redhat.rhsa:tst:20090057005
    • comment squirrelmail is signed with Red Hat master key
      oval oval:com.redhat.rhsa:tst:20070022003
  • AND
    • comment Red Hat Enterprise Linux 5 is installed
      oval oval:com.redhat.rhsa:tst:20070055001
    • comment squirrelmail is earlier than 0:1.4.8-5.el5_2.3
      oval oval:com.redhat.rhsa:tst:20090057007
    • comment squirrelmail is signed with Red Hat redhatrelease key
      oval oval:com.redhat.rhsa:tst:20070358008
rhsa
id RHSA-2009:0057
released 2009-01-19
severity Important
title RHSA-2009:0057: squirrelmail security update (Important)
rpms
  • squirrelmail-0:1.4.8-9.el3
  • squirrelmail-0:1.4.8-5.el4_7.3
  • squirrelmail-0:1.4.8-5.el5_2.3
refmap via4
apple APPLE-SA-2010-06-15-1
bid 34916
confirm
debian DSA-1802
fedora
  • FEDORA-2009-4870
  • FEDORA-2009-4875
  • FEDORA-2009-4880
mandriva MDVSA-2009:110
secunia
  • 35052
  • 35073
  • 35140
  • 40220
vupen
  • ADV-2009-1296
  • ADV-2010-1481
xf squirrelmail-baseuri-session-hijacking(50462)
Last major update 21-08-2010 - 00:00
Published 14-05-2009 - 13:30
Last modified 28-09-2017 - 21:34
Back to Top