Re: [Full-disclosure] Re: Advisory 18/2005: PHP Cross Site Scripting (XSS) Vulnerability in phpinfo()

From: Florian Weimer (fw_at_deneb.enyo.de)
Date: 10/31/05

  • Next message: Stefan Esser: "Re: [Full-disclosure] Re: Advisory 18/2005: PHP Cross Site Scripting (XSS) Vulnerability in phpinfo()" 
    To: Matthew Murphy <mattmurphy@kc.rr.com>
Date: Mon, 31 Oct 2005 20:45:55 +0100

    * Matthew Murphy:

    > Nice try, Stefan.
    >
    > I reported this vulnerability more than three years ago (against 4.2.x)
    > on October 12, 2002 via the PHP bug database. I was told to implement
    > an .ini setting and the bug was marked "Bogus".
    >
    > For information, please see PHP Bug #19881:
    > http://bugs.php.net/bug.php?id=19881

    For the record, Matthew's bug is CVE-2002-1954, and it appears to be
    unfixed. An URL which works with Internet Explorer against PHP 5.0.5
    is:

      http://localhost/test.php/"</img><script>alert();</script>

    This causes the passed JavaScript to be embedded into the PHP logo
    reference.

    Matthew's original exploit does not work anymore due to changes in the
    way requests are handled by Apache or PHP. However, it exposes an
    issue further down in the phpinfo output, which is triggered by
    Matthew's original URL:

      http://localhost/test.php?"><SCRIPT>alert(document.URL)</SCRIPT>=x

    There is not sufficent public information to tell which bug of the two
    is Stefan's. I'm not sure if the second URL qualifies as "stacked
    array assignment", so maybe Stefan discovered yet another problem.

    PS: Firefox %-encodes the URLs before sending them to the server, so
    these URLs do not work with that browser.
    _______________________________________________
    Full-Disclosure - We believe in it.
    Charter: http://lists.grok.org.uk/full-disclosure-charter.html
    Hosted and sponsored by Secunia - http://secunia.com/

  • Next message: Stefan Esser: "Re: [Full-disclosure] Re: Advisory 18/2005: PHP Cross Site Scripting (XSS) Vulnerability in phpinfo()"

    Relevant Pages

    • Re: php extensions compile error - another compile bug?
      ... Re: php extensions compile error - another compile bug?: ... Is not triviality is a matter of perspective? ... AFFECTS: users of PHP ... and shared extensions to allow more flexibility and add new features. ...
      (freebsd-questions)
    • Re: [Full-Disclosure] How secure is PHP ?
      ... > quick look at security focus, searching the vuln db for PHP, nothing more ... Looking at the Official PHP Bug list I am ... The PROGRAMMER is always supposed to validate user supplied ... validate the input it feeds to file system functions it is programmer error. ...
      (Full-Disclosure)
    • Re: Undefined Index notices
      ... I didn't say that it was a bug.. ... These are the first 3 lines of the script that gets posted to.. ... there is nothing but good php there. ... working with a n00b.. ...
      (comp.lang.php)
    • Re: List Fails on some computers - www missing in url
      ... Yes it is - for any domain issued - denying that simple fact allows PHP ... Why is this a security bug, whereas a user being able to erase his ... session cookie at any time and start a new session ISN'T just as ... NS records pointing at the DNS hosting company the domain owner is ...
      (comp.lang.php)
    • Re: Novice needs help :)
      ... you might want to either learn PHP or hire a consultant to give you a hand. ... Also, here on Usenet, we help people - but those people also need to be helping themselves. ... I don't have the several hours it could take to chase down a bug in that large of a chunk of code, and I doubt many people here do. ... I'd have to recreate your database, load it with data, then start testing. ...
      (comp.lang.php)
    • Quantcast