ID CVE-2008-2379
Summary Cross-site scripting (XSS) vulnerability in SquirrelMail before 1.4.17 allows remote attackers to inject arbitrary web script or HTML via a crafted hyperlink in an HTML part of an e-mail message.
References
Vulnerable Configurations
  • SquirrelMail 1.4.16
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.16
  • SquirrelMail 1.4.0
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.0
  • SquirrelMail 1.4.1
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.1
  • 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
  • SquirrelMail 1.4.2
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.2
  • SquirrelMail 1.4.3 -
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.3
  • 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.0_rc1
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.0_rc1
  • 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
  • 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
  • SquirrelMail 1.4.5 -
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.5
  • 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
  • SquirrelMail 1.4.7
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.7
  • cpe:2.3:a:squirrelmail:squirrelmail:1.4.5_rc1
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.5_rc1
  • SquirrelMail 1.4.8
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.8
  • 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
  • SquirrelMail 1.4.10
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.10
  • 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.15_rc1
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.15_rc1
  • SquirrelMail 1.4.15 -
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.15
  • 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.3.1
    cpe:2.3:a:squirrelmail:squirrelmail:1.3.1
  • cpe:2.3:a:squirrelmail:squirrelmail:1.3.2
    cpe:2.3:a:squirrelmail:squirrelmail:1.3.2
  • cpe:2.3:a:squirrelmail:squirrelmail:1.2.0_rc3
    cpe:2.3:a:squirrelmail:squirrelmail:1.2.0_rc3
  • SquirrelMail 1.2.0
    cpe:2.3:a:squirrelmail:squirrelmail:1.2.0
  • SquirrelMail 1.2.1
    cpe:2.3:a:squirrelmail:squirrelmail:1.2.1
  • SquirrelMail 1.2.2
    cpe:2.3:a:squirrelmail:squirrelmail:1.2.2
  • SquirrelMail 1.2.3
    cpe:2.3:a:squirrelmail:squirrelmail:1.2.3
  • SquirrelMail 1.2.4
    cpe:2.3:a:squirrelmail:squirrelmail:1.2.4
  • SquirrelMail 1.2.5
    cpe:2.3:a:squirrelmail:squirrelmail:1.2.5
  • SquirrelMail 1.2.6
    cpe:2.3:a:squirrelmail:squirrelmail:1.2.6
  • SquirrelMail 1.2.7
    cpe:2.3:a:squirrelmail:squirrelmail:1.2.7
  • 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.1
    cpe:2.3:a:squirrelmail:squirrelmail:1.1.1
  • 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.0pre1
    cpe:2.3:a:squirrelmail:squirrelmail:1.0pre1
  • cpe:2.3:a:squirrelmail:squirrelmail:1.0pre2
    cpe:2.3:a:squirrelmail:squirrelmail:1.0pre2
  • cpe:2.3:a:squirrelmail:squirrelmail:1.0pre3
    cpe:2.3:a:squirrelmail:squirrelmail:1.0pre3
  • SquirrelMail 1.0
    cpe:2.3:a:squirrelmail:squirrelmail:1.0
  • SquirrelMail 1.0.1
    cpe:2.3:a:squirrelmail:squirrelmail:1.0.1
  • SquirrelMail 1.0.2
    cpe:2.3:a:squirrelmail:squirrelmail:1.0.2
  • SquirrelMail 1.0.3
    cpe:2.3:a:squirrelmail:squirrelmail:1.0.3
  • SquirrelMail 1.0.4
    cpe:2.3:a:squirrelmail:squirrelmail:1.0.4
  • SquirrelMail 1.0.5
    cpe:2.3:a:squirrelmail:squirrelmail:1.0.5
  • SquirrelMail 1.0.6
    cpe:2.3:a:squirrelmail:squirrelmail:1.0.6
  • cpe:2.3:a:squirrelmail:squirrelmail:0.5pre1
    cpe:2.3:a:squirrelmail:squirrelmail:0.5pre1
  • cpe:2.3:a:squirrelmail:squirrelmail:0.5pre2
    cpe:2.3:a:squirrelmail:squirrelmail:0.5pre2
  • SquirrelMail 0.5
    cpe:2.3:a:squirrelmail:squirrelmail:0.5
  • cpe:2.3:a:squirrelmail:squirrelmail:0.4pre1
    cpe:2.3:a:squirrelmail:squirrelmail:0.4pre1
  • cpe:2.3:a:squirrelmail:squirrelmail:0.4pre2
    cpe:2.3:a:squirrelmail:squirrelmail:0.4pre2
  • SquirrelMail 0.4
    cpe:2.3:a:squirrelmail:squirrelmail:0.4
  • 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
  • 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.2
    cpe:2.3:a:squirrelmail:squirrelmail:0.2
  • SquirrelMail 0.2.1
    cpe:2.3:a:squirrelmail:squirrelmail:0.2.1
  • 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
CVSS
Base: 4.3 (as of 05-12-2008 - 08:56)
Impact:
Exploitability:
CWE CWE-79
CAPEC
  • Cross Site Scripting through Log Files
    An attacker may leverage a system weakness where logs are susceptible to log injection to insert scripts into the system's logs. If these logs are later viewed by an administrator through a thin administrative interface and the log data is not properly HTML encoded before being written to the page, the attackers' scripts stored in the log will be executed in the administrative interface with potentially serious consequences. This attack pattern is really a combination of two other attack patterns: log injection and stored cross site scripting.
  • Embedding Scripts in Non-Script Elements
    This attack is a form of Cross-Site Scripting (XSS) where malicious scripts are embedded in elements that are not expected to host scripts such as image tags (<img>), comments in XML documents (< !-CDATA->), etc. These tags may not be subject to the same input validation, output validation, and other content filtering and checking routines, so this can create an opportunity for an attacker to tunnel through the application's elements and launch a XSS attack through other elements. As with all remote attacks, it is important to differentiate the ability to launch an attack (such as probing an internal network for unpatched servers) and the ability of the remote attacker to collect and interpret the output of said attack.
  • Embedding Scripts within Scripts
    An attack of this type exploits a programs' vulnerabilities that are brought on by allowing remote hosts to execute scripts. The attacker leverages this capability to execute scripts to execute his/her own script by embedding it within other scripts that the target software is likely to execute. The attacker must have the ability to inject script into script that is likely to be executed. If this is done, then the attacker can potentially launch a variety of probes and attacks against the web server's local environment, in many cases the so-called DMZ, back end resources the web server can communicate with, and other hosts. With the proliferation of intermediaries, such as Web App Firewalls, network devices, and even printers having JVMs and Web servers, there are many locales where an attacker can inject malicious scripts. Since this attack pattern defines scripts within scripts, there are likely privileges to execute said attack on the host. Of course, these attacks are not solely limited to the server side, client side scripts like Ajax and client side JavaScript can contain malicious scripts as well. In general all that is required is for there to be sufficient privileges to execute a script, but not protected against writing.
  • Cross-Site Scripting in Error Pages
    An attacker distributes a link (or possibly some other query structure) with a request to a third party web server that is malformed and also contains a block of exploit code in order to have the exploit become live code in the resulting error page. When the third party web server receives the crafted request and notes the error it then creates an error message that echoes the malformed message, including the exploit. Doing this converts the exploit portion of the message into to valid language elements that are executed by the viewing browser. When a victim executes the query provided by the attacker the infected error message error message is returned including the exploit code which then runs in the victim's browser. XSS can result in execution of code as well as data leakage (e.g. session cookies can be sent to the attacker). This type of attack is especially dangerous since the exploit appears to come from the third party web server, who the victim may trust and hence be more vulnerable to deception.
  • Cross-Site Scripting Using Alternate Syntax
    The attacker uses alternate forms of keywords or commands that result in the same action as the primary form but which may not be caught by filters. For example, many keywords are processed in a case insensitive manner. If the site's web filtering algorithm does not convert all tags into a consistent case before the comparison with forbidden keywords it is possible to bypass filters (e.g., incomplete black lists) by using an alternate case structure. For example, the "script" tag using the alternate forms of "Script" or "ScRiPt" may bypass filters where "script" is the only form tested. Other variants using different syntax representations are also possible as well as using pollution meta-characters or entities that are eventually ignored by the rendering engine. The attack can result in the execution of otherwise prohibited functionality.
  • Cross-Site Scripting Using MIME Type Mismatch
    An attacker creates a file with scripting content but where the specified MIME type of the file is such that scripting is not expected. Some browsers will detect that the specified MIME type of the file does not match the actual type of the content and will automatically switch to using an interpreter for the real content type. If the browser does not invoke script filters before doing this, the attackers' script may run on the target unsanitized. For example, the MIME type text/plain may be used where the actual content is text/javascript or text/html. Since text does not contain scripting instructions, the stated MIME type would indicate that filtering is unnecessary. However, if the target application subsequently determines the file's real type and invokes the appropriate interpreter, scripted content could be invoked. In another example, img tags in HTML content could reference a renderable type file instead of an expected image file. The file extension and MIME type can describe an image file, but the file content can be text/javascript or text/html resulting in script execution. If the browser assumes all references in img tags are images, and therefore do not need to be filtered for scripts, this would bypass content filters. In a cross-site scripting attack, the attacker tricks the victim into accessing a URL that uploads a script file with an incorrectly specified MIME type. If the victim's browser switches to the appropriate interpreter without filtering, the attack will execute as a standard XSS attack, possibly revealing the victim's cookies or executing arbitrary script in their browser.
  • Cross-Site Scripting in Attributes
    The attacker inserts commands to perform cross-site scripting (XSS) actions in HTML attributes. Many filters do not adequately sanitize attributes against the presence of potentially dangerous commands even if they adequately sanitize tags. For example, dangerous expressions could be inserted into a style attribute in an anchor tag, resulting in the execution of malicious code when the resulting page is rendered. If a victim is tricked into viewing the rendered page the attack proceeds like a normal XSS attack, possibly resulting in the loss of sensitive cookies or other malicious activities.
  • Cross-Site Scripting via Encoded URI Schemes
    An attack of this type exploits the ability of most browsers to interpret "data", "javascript" or other URI schemes as client-side executable content placeholders. This attack consists of passing a malicious URI in an anchor tag HREF attribute or any other similar attributes in other HTML tags. Such malicious URI contains, for example, a base64 encoded HTML content with an embedded cross-site scripting payload. The attack is executed when the browser interprets the malicious content i.e., for example, when the victim clicks on the malicious link.
  • Cross-Site Scripting Using Doubled Characters, e.g. %3C%3Cscript
    The attacker bypasses input validation by using doubled characters in order to perform a cross-site scripting attack. Some filters fail to recognize dangerous sequences if they are preceded by repeated characters. For example, by doubling the < before a script command, (<<script or %3C%3script using URI encoding) the filters of some web applications may fail to recognize the presence of a script tag. If the targeted server is vulnerable to this type of bypass, the attacker can create a crafted URL or other trap to cause a victim to view a page on the targeted server where the malicious content is executed, as per a normal XSS attack.
  • Cross-Site Scripting Using Flash
    An attacker injects malicious script to global parameters in a Flash movie via a crafted URL. The malicious script is executed in the context of the Flash movie. As such, this is a form of Cross-Site Scripting (XSS), but the abilities granted to the Flash movie make this attack more flexible.
  • Cross-Site Scripting with Masking through Invalid Characters in Identifiers
    The attacker inserts invalid characters in identifiers to bypass application filtering of input. Filters may not scan beyond invalid characters but during later stages of processing content that follows these invalid characters may still be processed. This allows the attacker to sneak prohibited commands past filters and perform normally prohibited operations. Invalid characters may include null, carriage return, line feed or tab in an identifier. Successful bypassing of the filter can result in a XSS attack, resulting in the disclosure of web cookies or possibly other results.
  • Embedding Scripts in HTTP Query Strings
    A variant of cross-site scripting called "reflected" cross-site scripting, the HTTP Query Strings attack consists of passing a malicious script inside an otherwise valid HTTP request query string. This is of significant concern for sites that rely on dynamic, user-generated content such as bulletin boards, news sites, blogs, and web enabled administration GUIs. The malicious script may steal session data, browse history, probe files, or otherwise execute attacks on the client side. Once the attacker has prepared the malicious HTTP query it is sent to a victim user (perhaps by email, IM, or posted on an online forum), who clicks on a normal looking link that contains a poison query string. This technique can be made more effective through the use of services like http://tinyurl.com/, which makes very small URLs that will redirect to very large, complex ones. The victim will not know what he is really clicking on.
  • Simple Script Injection
    An attacker embeds malicious scripts in content that will be served to web browsers. The goal of the attack is for the target software, the client-side browser, to execute the script with the users' privilege level. An attack of this type exploits a programs' vulnerabilities that are brought on by allowing remote hosts to execute code and scripts. Web browsers, for example, have some simple security controls in place, but if a remote attacker is allowed to execute scripts (through injecting them in to user-generated content like bulletin boards) then these controls may be bypassed. Further, these attacks are very difficult for an end user to detect.
  • AJAX Fingerprinting
    This attack utilizes the frequent client-server roundtrips in Ajax conversation to scan a system. While Ajax does not open up new vulnerabilities per se, it does optimize them from an attacker point of view. In many XSS attacks the attacker must get a "hole in one" and successfully exploit the vulnerability on the victim side the first time, once the client is redirected the attacker has many chances to engage in follow on probes, but there is only one first chance. In a widely used web application this is not a major problem because 1 in a 1,000 is good enough in a widely used application. A common first step for an attacker is to footprint the environment to understand what attacks will work. Since footprinting relies on enumeration, the conversational pattern of rapid, multiple requests and responses that are typical in Ajax applications enable an attacker to look for many vulnerabilities, well-known ports, network locations and so on.
  • Embedding Script (XSS) in HTTP Headers
    An attack of this type exploits web applications that generate web content, such as links in a HTML page, based on unvalidated or improperly validated data submitted by other actors. XSS in HTTP Headers attacks target the HTTP headers which are hidden from most users and may not be validated by web applications.
  • XSS in IMG Tags
    Image tags are an often overlooked, but convenient, means for a Cross Site Scripting attack. The attacker can inject script contents into an image (IMG) tag in order to steal information from a victim's browser and execute malicious scripts.
Access
VectorComplexityAuthentication
NETWORK MEDIUM NONE
Impact
ConfidentialityIntegrityAvailability
NONE PARTIAL NONE
nessus via4
  • NASL family Red Hat Local Security Checks
    NASL id REDHAT-RHSA-2009-0010.NASL
    description An updated squirrelmail package that resolves various security issues is now available for Red Hat Enterprise Linux 3, 4 and 5. This update has been rated as having moderate 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. Ivan Markovic discovered a cross-site scripting (XSS) flaw in SquirrelMail caused by insufficient HTML mail sanitization. A remote attacker could send a specially crafted HTML mail or attachment that could cause a user's Web browser to execute a malicious script in the context of the SquirrelMail session when that email or attachment was opened by the user. (CVE-2008-2379) It was discovered that SquirrelMail allowed cookies over insecure connections (ie did not restrict cookies to HTTPS connections). An attacker who controlled the communication channel between a user and the SquirrelMail server, or who was able to sniff the user's network communication, could use this flaw to obtain the user's session cookie, if a user made an HTTP request to the server. (CVE-2008-3663) Note: After applying this update, all session cookies set for SquirrelMail sessions started over HTTPS connections will have the 'secure' flag set. That is, browsers will only send such cookies over an HTTPS connection. If needed, you can revert to the previous behavior by setting the configuration option '$only_secure_cookies' to 'false' in SquirrelMail's /etc/squirrelmail/config.php configuration file. Users of squirrelmail should upgrade to this updated package, which contains backported patches to correct these issues.
    last seen 2019-02-21
    modified 2019-01-02
    plugin id 35357
    published 2009-01-13
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=35357
    title RHEL 3 / 4 / 5 : squirrelmail (RHSA-2009:0010)
  • NASL family CentOS Local Security Checks
    NASL id CENTOS_RHSA-2009-0010.NASL
    description An updated squirrelmail package that resolves various security issues is now available for Red Hat Enterprise Linux 3, 4 and 5. This update has been rated as having moderate 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. Ivan Markovic discovered a cross-site scripting (XSS) flaw in SquirrelMail caused by insufficient HTML mail sanitization. A remote attacker could send a specially crafted HTML mail or attachment that could cause a user's Web browser to execute a malicious script in the context of the SquirrelMail session when that email or attachment was opened by the user. (CVE-2008-2379) It was discovered that SquirrelMail allowed cookies over insecure connections (ie did not restrict cookies to HTTPS connections). An attacker who controlled the communication channel between a user and the SquirrelMail server, or who was able to sniff the user's network communication, could use this flaw to obtain the user's session cookie, if a user made an HTTP request to the server. (CVE-2008-3663) Note: After applying this update, all session cookies set for SquirrelMail sessions started over HTTPS connections will have the 'secure' flag set. That is, browsers will only send such cookies over an HTTPS connection. If needed, you can revert to the previous behavior by setting the configuration option '$only_secure_cookies' to 'false' in SquirrelMail's /etc/squirrelmail/config.php configuration file. Users of squirrelmail should upgrade to this updated package, which contains backported patches to correct these issues.
    last seen 2019-02-21
    modified 2018-11-28
    plugin id 35353
    published 2009-01-13
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=35353
    title CentOS 3 / 4 / 5 : squirrelmail (CESA-2009:0010)
  • NASL family Oracle Linux Local Security Checks
    NASL id ORACLELINUX_ELSA-2009-0010.NASL
    description From Red Hat Security Advisory 2009:0010 : An updated squirrelmail package that resolves various security issues is now available for Red Hat Enterprise Linux 3, 4 and 5. This update has been rated as having moderate 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. Ivan Markovic discovered a cross-site scripting (XSS) flaw in SquirrelMail caused by insufficient HTML mail sanitization. A remote attacker could send a specially crafted HTML mail or attachment that could cause a user's Web browser to execute a malicious script in the context of the SquirrelMail session when that email or attachment was opened by the user. (CVE-2008-2379) It was discovered that SquirrelMail allowed cookies over insecure connections (ie did not restrict cookies to HTTPS connections). An attacker who controlled the communication channel between a user and the SquirrelMail server, or who was able to sniff the user's network communication, could use this flaw to obtain the user's session cookie, if a user made an HTTP request to the server. (CVE-2008-3663) Note: After applying this update, all session cookies set for SquirrelMail sessions started over HTTPS connections will have the 'secure' flag set. That is, browsers will only send such cookies over an HTTPS connection. If needed, you can revert to the previous behavior by setting the configuration option '$only_secure_cookies' to 'false' in SquirrelMail's /etc/squirrelmail/config.php configuration file. Users of squirrelmail should upgrade to this updated package, which contains backported patches to correct these issues.
    last seen 2019-02-21
    modified 2019-01-02
    plugin id 67786
    published 2013-07-12
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=67786
    title Oracle Linux 3 / 4 / 5 : squirrelmail (ELSA-2009-0010)
  • NASL family MacOS X Local Security Checks
    NASL id MACOSX_SECUPD2009-001.NASL
    description The remote host is running a version of Mac OS X 10.5 or 10.4 that does not have Security Update 2009-001 applied. This security update contains fixes for the following products : - AFP Server - Apple Pixlet Video - CarbonCore - CFNetwork - Certificate Assistant - ClamAV - CoreText - CUPS - DS Tools - fetchmail - Folder Manager - FSEvents - Network Time - perl - Printing - python - Remote Apple Events - Safari RSS - servermgrd - SMB - SquirrelMail - X11 - XTerm
    last seen 2019-02-21
    modified 2018-07-16
    plugin id 35684
    published 2009-02-13
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=35684
    title Mac OS X Multiple Vulnerabilities (Security Update 2009-001)
  • NASL family Scientific Linux Local Security Checks
    NASL id SL_20090112_SQUIRRELMAIL_ON_SL3_X.NASL
    description Ivan Markovic discovered a cross-site scripting (XSS) flaw in SquirrelMail caused by insufficient HTML mail sanitization. A remote attacker could send a specially crafted HTML mail or attachment that could cause a user's Web browser to execute a malicious script in the context of the SquirrelMail session when that email or attachment was opened by the user. (CVE-2008-2379) It was discovered that SquirrelMail allowed cookies over insecure connections (ie did not restrict cookies to HTTPS connections). An attacker who controlled the communication channel between a user and the SquirrelMail server, or who was able to sniff the user's network communication, could use this flaw to obtain the user's session cookie, if a user made an HTTP request to the server. (CVE-2008-3663) Note: After applying this update, all session cookies set for SquirrelMail sessions started over HTTPS connections will have the 'secure' flag set. That is, browsers will only send such cookies over an HTTPS connection. If needed, you can revert to the previous behavior by setting the configuration option '$only_secure_cookies' to 'false' in SquirrelMail's /etc/squirrelmail/config.php configuration file.
    last seen 2019-02-21
    modified 2019-01-02
    plugin id 60519
    published 2012-08-01
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=60519
    title Scientific Linux Security Update : squirrelmail on SL3.x, SL4.x, SL5.x i386/x86_64
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2008-10918.NASL
    description update to 1.4.17 fixes XSS issue caused by an insufficient html mail sanitation 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 2018-11-28
    plugin id 35048
    published 2008-12-08
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=35048
    title Fedora 8 : squirrelmail-1.4.17-1.fc8 (2008-10918)
  • NASL family SuSE Local Security Checks
    NASL id SUSE_SQUIRRELMAIL-5835.NASL
    description Insufficient input checks could allow remote attackers to conduct a cross site scripting (XSS) attack (CVE-2008-2379).
    last seen 2019-02-21
    modified 2014-06-13
    plugin id 35040
    published 2008-12-05
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=35040
    title openSUSE 10 Security Update : squirrelmail (squirrelmail-5835)
  • NASL family SuSE Local Security Checks
    NASL id SUSE_SQUIRRELMAIL-5860.NASL
    description This update brings squirrelmail to version 1.4.10a, fixing a previous regression in cookie handling (novell bug 446400) and a XSS problem (CVE-2008-2379).
    last seen 2019-02-21
    modified 2018-07-19
    plugin id 35184
    published 2008-12-16
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=35184
    title openSUSE 10 Security Update : squirrelmail (squirrelmail-5860)
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2008-10740.NASL
    description update to 1.4.17 fixes XSS issue caused by an insufficient html mail sanitation 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 2018-11-28
    plugin id 35044
    published 2008-12-08
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=35044
    title Fedora 9 : squirrelmail-1.4.17-1.fc9 (2008-10740)
  • NASL family FreeBSD Local Security Checks
    NASL id FREEBSD_PKG_D1CE8A4FC23511DD8CBC00163E000016.NASL
    description Squirrelmail team reports : An issue was fixed that allowed an attacker to send specially- crafted hyperlinks in a message that could execute cross-site scripting (XSS) when the user viewed the message in SquirrelMail.
    last seen 2019-02-21
    modified 2018-12-19
    plugin id 35037
    published 2008-12-05
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=35037
    title FreeBSD : squirrelmail -- XSS vulnerability (d1ce8a4f-c235-11dd-8cbc-00163e000016)
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2008-10748.NASL
    description update to 1.4.7 fixes: malformed HTML mail message script insertion 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 2015-10-21
    plugin id 37734
    published 2009-04-23
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=37734
    title Fedora 10 : squirrelmail-1.4.17-2.fc10 (2008-10748)
  • NASL family Debian Local Security Checks
    NASL id DEBIAN_DSA-1682.NASL
    description Ivan Markovic discovered that SquirrelMail, a webmail application, did not sufficiently sanitise incoming HTML email, allowing an attacker to perform cross site scripting through sending a malicious HTML email.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 35083
    published 2008-12-11
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=35083
    title Debian DSA-1682-1 : squirrelmail - insufficient input sanitising
oval via4
accepted 2013-04-29T04:21:58.061-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 Cross-site scripting (XSS) vulnerability in SquirrelMail before 1.4.17 allows remote attackers to inject arbitrary web script or HTML via a crafted hyperlink in an HTML part of an e-mail message.
family unix
id oval:org.mitre.oval:def:9764
status accepted
submitted 2010-07-09T03:56:16-04:00
title Cross-site scripting (XSS) vulnerability in SquirrelMail before 1.4.17 allows remote attackers to inject arbitrary web script or HTML via a crafted hyperlink in an HTML part of an e-mail message.
version 24
redhat via4
rpms
  • squirrelmail-0:1.4.8-8.el3
  • squirrelmail-0:1.4.8-5.el4_7.2
  • squirrelmail-0:1.4.8-5.el5_2.2
refmap via4
apple APPLE-SA-2009-02-12
bid 32603
confirm
debian DSA-1682
fedora
  • FEDORA-2008-10740
  • FEDORA-2008-10918
misc http://security-net.biz/wsw/index.php?p=254&n=190
secunia
  • 32143
  • 33054
  • 33071
  • 33937
suse SUSE-SR:2008:027
vupen ADV-2008-3332
xf squirrelmail-html-xss(47024)
Last major update 07-03-2011 - 22:09
Published 04-12-2008 - 19:30
Last modified 28-09-2017 - 21:31
Back to Top