Multi Ethnic Hacking Group

    FormMail 1.92 Multiple Remote Vulnerabilities


    Posts : 92
    Reputation : -1
    Join date : 2009-07-08

    FormMail 1.92 Multiple Remote Vulnerabilities Empty FormMail 1.92 Multiple Remote Vulnerabilities

    Post by Foxi on Wed Jul 08, 2009 4:16 am

    [code:1:f2da]FormMail 1.92 Multiple Vulnerabilities

    Name Multiple Vulnerabilities in FormMail
    Systems Affected FormMail 1.92 and possibly earlier versions
    Severity Medium
    Impact (CVSSv2) Medium 4.3/10, vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N)
    Authors Francesco "ascii" Ongaro (ascii AT ush DOT it)
    Giovanni "evilaliv3" Pellerano (evilaliv3 AT ush DOT it)
    Antonio "s4tan" Parata (s4tan AT ush DOT it)
    Date 20090511


    FormMail is a generic HTML form to e-mail gateway that parses the results
    of any form and sends them to the specified users. This script has many
    formatting and operational options, most of which can be specified within
    each form, meaning you don't need programming knowledge or multiple
    scripts for multiple forms. This also makes FormMail the perfect
    system-wide solution for allowing users form-based user feedback
    capabilities without the risks of allowing freedom of CGI access. There
    are several downloading options available below and more information on
    this script can be found in the Readme file. FormMail is quite possibily
    the most used CGI program on the internet, having been downloaded over
    2,000,000 times since 1997.

    II. DEscriptION

    Multiple Vulnerabilities exist in FormMail software.



    A) Prelude to the vulnerabities
    B) Cross Site scripting
    C) HTTP Response Header Injection
    D) HTTP Response Splitting

    A) Prelude to the vulnerabities

    What follows is the code used to validate the user input:

    Line 283: $safeConfig array definition.


    foreach $field (keys %Config) {
    $safeConfig{$field} = &clean_html($Config{$field});


    Line 518: definition of clean_html function, used to generate the
    "$safeConfig" array from "$Config".


    # This function will convert <, >, & and " to their HTML equivalents.
    sub clean_html {
    local $value = $_[0];
    $value =~ s/\&/\&/g;
    $value =~ s/</\</g;
    $value =~ s/>/\>/g;
    $value =~ s/"/\"/g;
    return $value;


    These functions are not always applied to the user input and don't
    protect against all the attack vectors (as URI or DOM XSS that can work
    also if encoded), this is why various vulnerabilities exist.

    B) Cross Site scripting vulnerability

    Line 293: the "redirect" variable is used to write the location header
    value. Its value is not filtered so it's possible to perform both
    HTTP Header Injection and an HTTP Response Splitting attacks.

    Since Header Injection is one of the most versatile attack vectors we
    could use it (like "downgrade it") to perform a Cross Site scripting
    attack but it would not represent a different vulnerability.

    In this case we are already inside a "Location" response header and it's
    possible to perform an XSS without splitting the response and using the
    standard Apache page for the 302 Found HTTP status.


    # If redirect option is used, print the redirectional location header.
    if ($Config{'redirect'}) {
    print "Location: $safeConfig{'redirect'}\n\n";


    XSS vulnerability example:


    $ curl -kis "


    HTTP/1.1 302 Found
    Date: Sat, 11 Apr 2009 14:12:11 GMT
    Server: Apache
    Location: javascript:alert('USH');
    Content-Length: 267
    Content-Type: text/html; charset=iso-8859-1
    <title>302 Found</title>
    <p>The document has moved <a href="javascript:alert('USH');">here</a>.</p>
    <address>Apache Server at Port 80</address>


    Obiously the XSS is not automatic since browsers don't follow the
    "javascript:" URI handler in the "Location" header.

    A second XSS vulnerability, not based on HTTP tricks, exists: in the
    following code the the "$return_link" variable is reflected (printed) in
    the page body without any validation:


    Line 371: the "$return_link" variable is printed in the page body
    without any validation.


    # Check for a Return Link and print one if found. #
    if ($Config{'return_link_url'} && $Config{'return_link_title'}) {
    print "<ul>\n";
    print "<li><a href=\"$safeConfig{'return_link_url'}\">$safeConfig{'return_link_title'}</a>\n";
    print "</ul>\n";


    The vulnerability can be triggered with the following request:

    $ curl -kis "

    This XSS is not automatic.

    C) HTTP Response Header Injection

    An HTTP Response Header Injection vulnerability exists, the following
    request triggers the vulnerability:

    $ curl -kis "

    Can be verified with the obvious "javascript:alert(document

      Current date/time is Mon Jun 17, 2019 7:23 am