Home    |    View Topics    |    Search    |    Contact Us    |   



Category:   Application (Multimedia)  >   SGallery Vendors:   Kiselev, Sergey
SGallery Input Validation Holes Let Remote Users Inject SQL Commands and Potentially Execute Arbitrary Commands
SecurityTracker Alert ID:  1012868
SecurityTracker URL:
CVE Reference:   GENERIC-MAP-NOMATCH   (Links to External Site)
Updated:  Jan 14 2005
Original Entry Date:  Jan 13 2005
Impact:   Disclosure of system information, Disclosure of user information, Execution of arbitrary code via network, User access via network
Exploit Included:  Yes  
Version(s): 1.01
Description:   An input validation vulnerability was reported in the SGallery module for PHP-Nuke. A remote user can inject SQL commands and determine the installation path. In some cases, a remote user can execute arbitrary commands on the target system.

Janek Vind "waraxe" reported that, depending on the configuration, a remote user may be able to supply a specially crafted URL to cause arbitrary PHP code to be included by and executed on the target server.

The 'imageview.php' script does not properly validate user-supplied input in the 'idalbum' and 'idimage' variables. A remote user can supply a specially crafted request to execute SQL commands on the underlying database.

A demonstration exploit URL is provided:


A remote user can also submit a request to cause the system to disclose the installation path. If both the 'idalbum' and 'idimage' variables are not set, this can be triggered.

The vendor was notified on November 16, 2004, without response.

The original advisory is available at:

Impact:   A remote user can execute SQL commands on the underlying database.

A remote user can determine the installation path.

A remote user may be able to execute arbitrary PHP code and operating system commands on the target system with the privileges of the target web service.

Solution:   No solution was available at the time of this entry.
Vendor URL: (Links to External Site)
Cause:   Input validation error
Underlying OS:  Linux (Any), UNIX (Any)

Message History:   None.

 Source Message Contents

Subject:  [waraxe-2005-SA#039] - Critical Sql Injection in Sgallery module

{                              [waraxe-2005-SA#039]                              }
{                                                                                }
{             [ Critical Sql Injection in Sgallery module for PhpNuke ]          }
{                                                                                }
Author: Janek Vind "waraxe"
Date: 12. January 2005
Location: Estonia, Tartu

Affected software description:

Module's Name: SGallery
Module's Version: 1.01
Module's Description: Simple JPG image gallery
License: GNU/GPL
Author's Name: Sergey Kiselev
Author's Email:



Let's look at source code from imageview.php:

----------------[ original code ]---------------

  $dbi = sql_connect ($dbhost,$dbuname,$dbpass,$dbname);

  if ($idalbum) {
    $result = sql_query("select picture from ".$prefix."_SGalbums where idalbum=".$idalbum,$dbi);
  } elseif ($idimage) {
    $result = sql_query("select picture from ".$prefix."_SGimages where idimage=".$idimage,$dbi);

  list($echo) = sql_fetch_row($result, $dbi);

  sql_logout ($dbi);

  header ("Content-Type: image/jpeg");
  echo $echo;

----------------[ /original code ]---------------

Now let's analyze the weak points.

A - Full Path Disclosure

If "$idalbum" and "$idimage" are both unset, then because of the open "if/elseif" construction
there variable "$result" will be unset or can be poisoned through GET/POST/COOKIE.
And next call of the "sql_fetch_row()" will trigger generic php error messages, leading to
full path disclosure. Path disclosure is considered as low level security threat, but anyway it's
useful for further malicious actions.

B - Potential arbitrary file inclusion:

This kind of code construction as


is not very secure. Depending of the webserver software vendor,version number and configuration
settings it can lead to arbitrary file inclusion and possible remote file inclusion.

C - Critical sql injection bug in "imageview.php":

Looking at source code, presented above, we can see unsecure sql queries directed to the database.
To be excact, user submitted variables "$idalbum" and/or "$idimage" are used in sql "SELECT" clause
without escaping with single quotes. This is clearly sql injection bug. Further exploitation will
depend on database software and version. In case of the mysql version 4.x with UNION functionality enabled,
arbitrary data can be retrieved from database, inluding admin(s) authentication credentials.
Traditionally, there is the proof of concept:

----------------[ real life exploit ]---------------


----------------[/real life exploit ]---------------

Best browser to test this POC is MSIE - it will show plaintext admin password's md5 hash as needed.
Firefox and other browsers will mostly rendering out "broken picture" because of the
"Content-Type: image/jpeg" header. But anyway, sql injection exists, can be exploited and must be
fixed by vendor as soon as possible.

How to fix:

Developer first contacted: 16. November 2004
No response from developer after multiple sent emails.
Downloadable version of the Sgalley is still unpatched.

How to fix this security hole -

Additional resources:

Base64 encoder and decoder -
SiteMapper - free php script for phpNuke powered websites -
It's easy to install solution for making phpNuke more Google friendly!


Greets to icenix, Raido Kerna, g0df4th3r and slimjim100!
Tervitused - Heintz!

    Janek Vind "waraxe"


---------------------------------- [ EOF ] ------------------------------------


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 2022, LLC