|
dotProject Multiple Vulnerabilities
|
|
Secunia Advisory:
|
SA31681
|
|
|
Release Date:
|
2008-08-29
|
|
Last Update:
|
2009-03-25
|
|
Popularity:
|
4,024 views
|
|
|
Critical:
|
Less critical
|
|
Impact:
|
Cross Site Scripting
Manipulation of data
Exposure of sensitive information
|
|
Where:
|
From remote
|
|
Solution Status:
|
Unpatched
|
|
| Software: | dotProject 2.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 dotProject, which can be exploited by malicious users to conduct SQL injection and script insertion attacks, and by malicious people to conduct cross-site scripting and request forgery attacks.
1) Input passed to the "inactive" parameter in index.php (when "m" is set to "tasks"), "date" in index.php (when "m" is set to "calendar" and "a" to "day_view"), "callback" in index.php (when "m" is set to "public", "a" is set to "calendar", and "dialog" is set to "1"), and "type" in index.php (when "m" is set to "ticketsmith") is not 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 of this vulnerability requires that the target user has valid user credentials.
2) Input passed to the "tab" parameter in index.php (when "m" is set to "projects") 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 of this vulnerability allows e.g. retrieval of administrator usernames and password hashes, but requires valid user credentials.
3) Input passed to the "user_id" parameter in index.php (when "m" is set to "admin" and "a" to "viewuser") 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 of this vulnerability requires valid administrator credentials.
4) Input passed to the "event_title" and "event_description" parameters in index.php (when "m" is set to "calendar") is not properly sanitised before being used. This can exploited to insert arbitrary HTML and script code, which will be executed in a user's browser session in the context of an affected site if the malicious event is viewed.
5) Input passed to the "company_name", "company_email", "company_phone1", "company_phone2", "company_fax", "company_address1", "company_address2", "company_city", "company_state", "company_zip", "company_primary_url", and "company_description" parameters in index.php (when "m" is set to "companies") is not properly sanitised before being used. This can exploited to insert arbitrary HTML and script code, which will be executed in a user's browser session in the context of an affected site if the malicious company details are viewed.
Successful exploitation of vulnerabilities #4 and #5 requires a valid user account.
6) The application allows users to perform certain actions via HTTP requests without performing any validity checks to verify the requests. This can be exploited to e.g. create user accounts by enticing a logged in administrator to visit a malicious web page.
The vulnerabilities are confirmed in version 2.1.2. 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 Jul, 2009
|
New advisories:
|
20 |
|
New vulnerabilities:
|
79 |
|
Updated advisories:
|
40 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
 Solutions | More...
|
|
