ID CVE-2009-1581
Summary functions/mime.php in SquirrelMail before 1.4.18 does not protect the application's content from Cascading Style Sheets (CSS) positioning in HTML e-mail messages, which allows remote attackers to spoof the user interface, and conduct cross-site scripting (XSS) and phishing attacks, via a crafted message.
References
Vulnerable Configurations
  • 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.15
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.15
  • 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.11
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.11
  • 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.10
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.10
  • 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.0_rc2a
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.0_rc2a
  • 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.2.9
    cpe:2.3:a:squirrelmail:squirrelmail:1.2.9
  • cpe:2.3:a:squirrelmail:squirrelmail:1.4
    cpe:2.3:a:squirrelmail:squirrelmail:1.4
  • 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.4.0_rc1
    cpe:2.3:a:squirrelmail:squirrelmail:1.4.0_rc1
  • 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.6
    cpe:2.3:a:squirrelmail:squirrelmail:1.2.6
  • 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.2
    cpe:2.3:a:squirrelmail:squirrelmail:1.3.2
  • 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.2.0
    cpe:2.3:a:squirrelmail:squirrelmail:1.2.0
  • cpe:2.3:a:squirrelmail:squirrelmail:1.2
    cpe:2.3:a:squirrelmail:squirrelmail:1.2
  • 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.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.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.1
    cpe:2.3:a:squirrelmail:squirrelmail:1.2.1
  • 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.10
    cpe:2.3:a:squirrelmail:squirrelmail:1.2.10
  • 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.0.5
    cpe:2.3:a:squirrelmail:squirrelmail:1.0.5
  • cpe:2.3:a:squirrelmail:squirrelmail:1.0pre2
    cpe:2.3:a:squirrelmail:squirrelmail:1.0pre2
  • 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.0pre3
    cpe:2.3:a:squirrelmail:squirrelmail:1.0pre3
  • 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.0
    cpe:2.3:a:squirrelmail:squirrelmail:1.0
  • cpe:2.3:a:squirrelmail:squirrelmail:0.4
    cpe:2.3:a:squirrelmail:squirrelmail:0.4
  • 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: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
  • cpe:2.3:a:squirrelmail: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
  • cpe:2.3:a:squirrelmail:squirrelmail:0.1
    cpe:2.3:a:squirrelmail:squirrelmail:0.1
  • 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.2
    cpe:2.3:a:squirrelmail:squirrelmail:0.2
  • 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.3
    cpe:2.3:a:squirrelmail:squirrelmail:0.3
  • cpe:2.3:a:squirrelmail:squirrelmail:0.3pre2
    cpe:2.3:a:squirrelmail:squirrelmail:0.3pre2
  • cpe:2.3:a:squirrelmail:squirrelmail:0.3pre1
    cpe:2.3:a:squirrelmail:squirrelmail:0.3pre1
  • SquirrelMail
    cpe:2.3:a:squirrelmail:squirrelmail
  • 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.1.1
    cpe:2.3:a:squirrelmail:squirrelmail:0.1.1
  • 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
CVSS
Base: 4.3 (as of 15-05-2009 - 10:41)
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 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 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 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 Scientific Linux Local Security Checks
    NASL id SL_20090526_SQUIRRELMAIL_ON_SL3_X.NASL
    description A server-side code injection flaw was found in the SquirrelMail 'map_yp_alias' function. If SquirrelMail was configured to retrieve a user's IMAP server address from a Network Information Service (NIS) server via the 'map_yp_alias' function, an unauthenticated, remote attacker using a specially crafted username could use this flaw to execute arbitrary code with the privileges of the web server. (CVE-2009-1579) Multiple cross-site scripting (XSS) flaws were found in SquirrelMail. An attacker could construct a carefully crafted URL, which once visited by an unsuspecting user, could cause the user's web browser to execute malicious script in the context of the visited SquirrelMail web page. (CVE-2009-1578) It was discovered that SquirrelMail did not properly sanitize Cascading Style Sheets (CSS) directives used in HTML mail. A remote attacker could send a specially crafted email that could place mail content above SquirrelMail's controls, possibly allowing phishing and cross-site scripting attacks. (CVE-2009-1581)
    last seen 2019-02-21
    modified 2019-01-02
    plugin id 60590
    published 2012-08-01
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=60590
    title Scientific Linux Security Update : squirrelmail on SL3.x, SL4.x, SL5.x i386/x86_64
  • NASL family Red Hat Local Security Checks
    NASL id REDHAT-RHSA-2009-1066.NASL
    description An updated squirrelmail package that fixes multiple security issues 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 a standards-based webmail package written in PHP. A server-side code injection flaw was found in the SquirrelMail 'map_yp_alias' function. If SquirrelMail was configured to retrieve a user's IMAP server address from a Network Information Service (NIS) server via the 'map_yp_alias' function, an unauthenticated, remote attacker using a specially crafted username could use this flaw to execute arbitrary code with the privileges of the web server. (CVE-2009-1579) Multiple cross-site scripting (XSS) flaws were found in SquirrelMail. An attacker could construct a carefully crafted URL, which once visited by an unsuspecting user, could cause the user's web browser to execute malicious script in the context of the visited SquirrelMail web page. (CVE-2009-1578) It was discovered that SquirrelMail did not properly sanitize Cascading Style Sheets (CSS) directives used in HTML mail. A remote attacker could send a specially crafted email that could place mail content above SquirrelMail's controls, possibly allowing phishing and cross-site scripting attacks. (CVE-2009-1581) 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-27
    plugin id 38922
    published 2009-05-27
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=38922
    title RHEL 3 / 4 / 5 : squirrelmail (RHSA-2009:1066)
  • 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 Oracle Linux Local Security Checks
    NASL id ORACLELINUX_ELSA-2009-1066.NASL
    description From Red Hat Security Advisory 2009:1066 : An updated squirrelmail package that fixes multiple security issues 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 a standards-based webmail package written in PHP. A server-side code injection flaw was found in the SquirrelMail 'map_yp_alias' function. If SquirrelMail was configured to retrieve a user's IMAP server address from a Network Information Service (NIS) server via the 'map_yp_alias' function, an unauthenticated, remote attacker using a specially crafted username could use this flaw to execute arbitrary code with the privileges of the web server. (CVE-2009-1579) Multiple cross-site scripting (XSS) flaws were found in SquirrelMail. An attacker could construct a carefully crafted URL, which once visited by an unsuspecting user, could cause the user's web browser to execute malicious script in the context of the visited SquirrelMail web page. (CVE-2009-1578) It was discovered that SquirrelMail did not properly sanitize Cascading Style Sheets (CSS) directives used in HTML mail. A remote attacker could send a specially crafted email that could place mail content above SquirrelMail's controls, possibly allowing phishing and cross-site scripting attacks. (CVE-2009-1581) Users of squirrelmail should upgrade to this updated package, which contains backported patches to correct these issues.
    last seen 2019-02-21
    modified 2016-12-07
    plugin id 67865
    published 2013-07-12
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=67865
    title Oracle Linux 3 / 4 / 5 : squirrelmail (ELSA-2009-1066)
  • 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 CentOS Local Security Checks
    NASL id CENTOS_RHSA-2009-1066.NASL
    description An updated squirrelmail package that fixes multiple security issues 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 a standards-based webmail package written in PHP. A server-side code injection flaw was found in the SquirrelMail 'map_yp_alias' function. If SquirrelMail was configured to retrieve a user's IMAP server address from a Network Information Service (NIS) server via the 'map_yp_alias' function, an unauthenticated, remote attacker using a specially crafted username could use this flaw to execute arbitrary code with the privileges of the web server. (CVE-2009-1579) Multiple cross-site scripting (XSS) flaws were found in SquirrelMail. An attacker could construct a carefully crafted URL, which once visited by an unsuspecting user, could cause the user's web browser to execute malicious script in the context of the visited SquirrelMail web page. (CVE-2009-1578) It was discovered that SquirrelMail did not properly sanitize Cascading Style Sheets (CSS) directives used in HTML mail. A remote attacker could send a specially crafted email that could place mail content above SquirrelMail's controls, possibly allowing phishing and cross-site scripting attacks. (CVE-2009-1581) 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-10
    plugin id 38930
    published 2009-05-28
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=38930
    title CentOS 3 / 5 : squirrelmail (CESA-2009:1066)
  • 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:05:43.499-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 functions/mime.php in SquirrelMail before 1.4.18 does not protect the application's content from Cascading Style Sheets (CSS) positioning in HTML e-mail messages, which allows remote attackers to spoof the user interface, and conduct cross-site scripting (XSS) and phishing attacks, via a crafted message.
family unix
id oval:org.mitre.oval:def:10441
status accepted
submitted 2010-07-09T03:56:16-04:00
title functions/mime.php in SquirrelMail before 1.4.18 does not protect the application's content from Cascading Style Sheets (CSS) positioning in HTML e-mail messages, which allows remote attackers to spoof the user interface, and conduct cross-site scripting (XSS) and phishing attacks, via a crafted message.
version 24
redhat via4
advisories
bugzilla
id 500363
title CVE-2009-1578 SquirrelMail: Multiple cross site scripting issues
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-13.el3
      oval oval:com.redhat.rhsa:tst:20091066002
    • 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_8.5
      oval oval:com.redhat.rhsa:tst:20091066005
    • 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_3.7
      oval oval:com.redhat.rhsa:tst:20091066007
    • comment squirrelmail is signed with Red Hat redhatrelease key
      oval oval:com.redhat.rhsa:tst:20070358008
rhsa
id RHSA-2009:1066
released 2009-05-26
severity Important
title RHSA-2009:1066: squirrelmail security update (Important)
rpms
  • squirrelmail-0:1.4.8-13.el3
  • squirrelmail-0:1.4.8-5.el4_8.5
  • squirrelmail-0:1.4.8-5.el5_3.7
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
  • 35259
  • 40220
vupen
  • ADV-2009-1296
  • ADV-2010-1481
xf squirrelmail-css-xss(50463)
Last major update 21-08-2010 - 01:32
Published 14-05-2009 - 13:30
Last modified 28-09-2017 - 21:34
Back to Top