|
The Address Book Multiple Vulnerabilities
|
|
Secunia Advisory:
|
SA21694
|
|
|
Release Date:
|
2007-01-03
|
|
Popularity:
|
7,123 views
|
|
|
Critical:
|
Highly critical
|
|
Impact:
|
Hijacking
Security Bypass
Cross Site Scripting
Manipulation of data
Exposure of sensitive information
System access
|
|
Where:
|
From remote
|
|
Solution Status:
|
Unpatched
|
|
| Software: | The Address Book 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:
Secunia Research has discovered some vulnerabilities and a security issue in The Address Book, which can be exploited by malicious people to bypass certain security restrictions, conduct cross-site scripting, cross-site request forgery, script insertion, and SQL injection attacks, disclose sensitive information, and compromise a vulnerable system.
1) Input passed to the "lastname" and "firstname" parameters when adding a new entry, the "passwordOld" and "passwordNew" parameters when changing the password in users.php, the "id" parameter when confirming a user in users.php, the "language" and "defaultLetter" parameters when changing personal options in users.php, the "goTo" and "search" parameters in search.php during searches, the "groupAddName" parameter when adding a new group in save.php, and the "newuserPass", "newuserType", and "newuserEmail" parameters when an administrator adds a user in users.php isn't properly sanitised before being used in a SQL query. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.
Successful exploitation requires that "magic_quotes_gpc" is disabled (except for the "id" parameter).
2) An input validation error exists in the picture upload handling due to missing verification of the content of uploaded images. This can be exploited to execute arbitrary HTML and script code in a user's browser session in context of an affected site when a specially crafted HTML document with the ".gif" or ".jpg" file extension is viewed directly in the Microsoft Internet Explorer browser.
3) Input passed to the "email" and "websites" parameters when adding a new entry, and the "groupAddName" parameter when adding a new group in save.php isn't properly sanitised before being used. This can be exploited to inject arbitrary HTML and script code, which will be executed in a user's browser session in context of an affected site when the malicious user data is viewed.
Example:
Adding new entry: " onmouseover=[code] "
4) The problem is that user credentials are included in the exported MySQL dump file generated by export.php which is accessible by normal users. This can be exploited to disclose usernames and encrypted passwords (MD5 sum).
5) Input passed to the "language" parameter when changing personal options in users.php isn't properly verified, before it is used to include files. This can be exploited to include arbitrary files from local resources.
This can further be exploited to include arbitrary PHP code injected into uploaded image files.
Example:
../mugshots/[file].gif%00
6) Input passed to the "errorMsg" parameter in index.php, and the "goTo" and "search" parameters in search.php 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.
Successful exploitation requires that "register_globals" is enabled (except for the "goTo" parameter).
7) The problem is that it is possible to register a new user account in register.php even when "Allow User Self-Registration" has been disabled by setting the "mode" parameter to "confirm".
8) An error exists in the picture upload handling due to the application only validating the "Content-Type" header and not the file extension. This can be exploited to upload a malicious PHP script inside the web root.
9) An error exists due to the application allowing users to perform certain actions via HTTP requests without performing any validity checks to verify the user's request.
Example:
http://[host]/users.php?action=deleteuser&id=[id]
The vulnerabilities and the security issue are confirmed in version 1.04e. 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.
|
|
|
6th Nov, 2009
|
New advisories:
|
17 |
|
New vulnerabilities:
|
65 |
|
Updated advisories:
|
21 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
 Solutions | More...
|
|
