SecurityTracker.com
    Home    |    View Topics    |    Search    |    Contact Us    |   

SecurityTracker
Archives


 


Category:   Application (Forum/Board/Portal)  >   eXpBlog Vendors:   expblog.de
eXpBlog Input Validation Holes in 'kalender.php' and 'pre_details.php' Permit Cross-Site Scripting Attacks
SecurityTracker Alert ID:  1017028
SecurityTracker URL:  http://securitytracker.com/id/1017028
CVE Reference:   CVE-2006-5239   (Links to External Site)
Updated:  Jun 2 2008
Original Entry Date:  Oct 10 2006
Impact:   Disclosure of authentication information, Disclosure of user information, Execution of arbitrary code via network, Modification of user information
Exploit Included:  Yes  
Version(s): 0.3.5 and prior versions
Description:   A vulnerability was reported in eXpBlog. A remote user can conduct cross-site scripting attacks.

The 'kalender.php' and 'pre_details.php' scripts do not properly filter HTML code from user-supplied input before displaying the input. A remote user can create a specially crafted URL that, when loaded by a target user, will cause arbitrary scripting code to be executed by the target user's browser. The code will originate from the site running the eXpBlog software and will run in the security context of that site. As a result, the code will be able to access the target user's cookies (including authentication cookies), if any, associated with the site, access data recently submitted by the target user via web form to the site, or take actions on the site acting as the target user.

Some demonstration exploit URL portions are provided:

details.php/%3E%22%3E%3Cscript%3Ealert('Unsecure')%3C/script%3E

comment=1&captcha_session_code=>"><script>alert('hole')</script>...

The vendor was notified on October 3, 2006.

Tamriel reported this vulnerability.

Impact:   A remote user can access the target user's cookies (including authentication cookies), if any, associated with the site running the eXpBlog software, access data recently submitted by the target user via web form to the site, or take actions on the site acting as the target user.
Solution:   No solution was available at the time of this entry.

An unofficial security fix is available at:

http://www.expblog.de/board/viewtopic.php?t=317

Vendor URL:  www.expblog.de/ (Links to External Site)
Cause:   Input validation error
Underlying OS:  Linux (Any), UNIX (Any), Windows (Any)

Message History:   None.


 Source Message Contents

Subject:  [Full-disclosure] eXpBlog <= 0.3.5 Cross Site Scripting

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
 
      Advisory: eXpBlog <= 0.3.5 Cross Site Scripting Vulnerabilities
  Release Date: 10/09/2006
 Last Modified: 10/09/2006
        Author: Tamriel [tamriel <at> gmx <dot> net]
   Application: eXpBlog <= 0.3.5
          Risk: Low
 Vendor Status: contaced | replied
   Vendor Site: www.expblog.de


 Overview:

   Quote from www.expblog.de:

   "Das eXpBlog ist eine beliebte Freeware weBlog Software basierend
    auf PHP und mySQL. Mit einem eXpBlog verfuegen Sie ueber ein
    flexibles und schnelles Mehrbenutzer-weBlog welches durch ein
    Plugin-System komfortabel erweiterbar ist."

   There are some cross site scripting vulnerabilities which can
   be exploited by malicious people to conduct script insertion attacks.

   The vulnerability has been discovered in the latest version. Other
   versions may also be affected.


 Details:
 
   1) Cross Site Scripting Vulnerability in kalender.php

      Arround the lines 130-140 the variable `$_SERVER['PHP_SELF']` is
      not properly sanitised before being used. This can be exploited
      to insert arbitrary HTML and script code, which is executed in a
      user's browser session in context of an affected site when the
      malicious data is viewed.

   2) Cross Site Scripting Vulnerability in pre_details.php

      Arround the lines 15-20 the variable
      `$_POST["captcha_session_code"]` is not properly sanitised before
      being used. This variable is used in the details.php arround
      line 152, here an attacker can insert malicious code. The
      captcha class may be affected too, because you can let it open a
      special file (captcha_class.php, arround line 140).


 Proof of Concept:

   1) details.php/%3E%22%3E%3Cscript%3Ealert('Unsecure')%3C/script%3E

   2) comment=1&captcha_session_code=>"><script>alert('hole')</script>...


 Solution/Fix:

      Edit the source code to ensure that input is properly sanitised.
      Use functions like PHP`s htmlentities() function.

 Disclosure Timeline:

      10/03/2006 - Discovery of the vulnerabilities
      10/03/2006 - Contacted the vendor
      10/04/2006 - Vendor reponse
      10/09/2006 - Supplied bugfix to the official forum
      10/09/2006 - Public disclosure

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
 
iD8DBQFFKry2qBhP+Twks7oRClOMAJwLn7OE+fmHEtPKvXm0K3k33I0UwQCglO9r
Qq56AylXMq1S9uGFnb0WapA=
=lXZq
-----END PGP SIGNATURE-----


_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/

 
 


Go to the Top of This SecurityTracker Archive Page





Home   |    View Topics   |    Search   |    Contact Us

This web site uses cookies for web analytics. Learn More

Copyright 2021, SecurityGlobal.net LLC