|
Jupiter Content Manager Multiple Vulnerabilities
|
|
Secunia Advisory:
|
SA19582
|
|
|
Release Date:
|
2006-04-11
|
|
Last Update:
|
2007-02-22
|
|
Popularity:
|
7,028 views
|
|
|
Critical:
|
Highly critical
|
|
Impact:
|
Cross Site Scripting
Manipulation of data
Exposure of system information
Exposure of sensitive information
System access
|
|
Where:
|
From remote
|
|
Solution Status:
|
Unpatched
|
|
| Software: | Jupiter Content Manager 1.x
|
|
|
Secunia CVSS-2 Score:
|
Available in Secunia business solutions 
|
|
|
Subscribe:
|
Instant alerts on relevant vulnerabilities
|
|
| Advisory Content (Page 1 of 3) | [ 1 ] [ 2 ] [ 3 ] | |
|
Description:
Some vulnerabilities have been discovered in Jupiter Content Manager, which can be exploited by malicious people to conduct cross-site scripting and SQL injection attacks, disclose sensitive information, and compromise a vulnerable system.
1) Input passed to the "layout" parameter in index.php and the "language[]" parameter array in multiple files isn't properly sanitised before being returned to the user. This can be exploited to execute arbitrary HTML and script code in a user's browser session in context of an affected site.
Examples:
http://[host]/index.php?n=modules/online&&a=1&language=1&layout=[code]
http://[host]/modules/blocks.php?is_webmaster=2&language[Admin%20name]=[code]
http://[host]/modules/register.php?is_guest=1&language[Register%20title]=[code]
http://[host]/modules/mass-email.php?language[Mass-Email%20form%20title]=[code]
http://[host]/modules/search.php?language[Search%20view%20desc]=[code]
Note: More entries of the "language[]" parameter array can be used for exploitation.
2) Input passed to the "n" parameter in "index.php" isn't properly verified, before it is used to include files. This can be exploited to include arbitrary files from local or external resources.
This can further be exploited to include arbitrary PHP code injected into uploaded avatar images.
Successful exploitation with arbitrary file extensions on local resources requires that "magic_quotes_gpc" is disabled.
Successful exploitation on external resources requires that the system is running PHP 5 or later.
3) Input passed to the "username" form field parameter when logging in, to the "fpwusername" and "fpwemail" form field parameters, and to the "key" parameter in index.php is not properly sanitised before being used in a SQL query. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.
Successful exploitation e.g. allows access to the administration section but requires that "magic_quotes_gpc" is disabled.
4) Input passed in the "Client-IP", "X-Forwarded-For", "X-Forwarded", "Forwarded-For" and "Forwarded" HTTP headers to index.php is not properly sanitised before being used in SQL queries. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.
Successful exploitation allows e.g. retrieving usernames and password hashes.
5) Input passed to the "Referer" HTTP header in index.php is not properly sanitised before being stored. This can be exploited to insert arbitrary HTML and script code, which is executed in an administrator's browser session in context of an affected site when the administrator views the data with the "Logged Guests" function.
The vulnerabilities have been confirmed in version 1.1.5. Other versions may also be affected.
Change Page:
[ 1 ] [ 2 ] [ 3 ]
|
|
|
Track this Secunia Advisory
|
Customers of the Secunia Vulnerability Intelligence solutions will automatically receive updates when new information regarding this advisory is released.
Read more about our Vulnerability Intelligence solutions and what they can do for you and your company.
|
|
|
About this Secunia Advisory
|
Please note: The information that this Secunia Advisory is based on comes from a third party unless stated otherwise.
Secunia collects, validates, and verifies all vulnerability reports issued by security research groups, vendors, and others.
|
