|
myEvent Multiple Vulnerabilities
|
|
Secunia Advisory:
|
SA19680
|
|
|
Release Date:
|
2006-04-18
|
|
Last Update:
|
2006-08-18
|
|
Popularity:
|
7,025 views
|
|
|
Critical:
|
Highly critical
|
|
Impact:
|
Cross Site Scripting
Manipulation of data
System access
|
|
Where:
|
From remote
|
|
Solution Status:
|
Unpatched
|
|
| Software: | myEvent 1.x
|
|
|
Subscribe:
|
Instant alerts on relevant vulnerabilities 
|
|
| CVE reference: | CVE-2006-1890
CVE-2006-1907
CVE-2006-1908
CVE-2006-4040
CVE-2006-4083
|
|
Description:
Some vulnerabilities have been discovered in myEvent, which can be exploited by malicious users to conduct script insertion and SQL injection attacks, and by malicious people to compromise a vulnerable system.
1) Input passed to the "event_desc" parameter in addevent.php is not properly sanitised before being used. 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 malicious event is viewed.
2) Input passed to the "event_id" parameter in addevent.php and del.php, and to the "event_desc" in addevent.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.
3) Input passed to the "myevent_path" parameter in event.php and initialize.php is not properly verified before being used to include files. This can be exploited to execute arbitrary PHP code by including PHP files from local or external resources.
4) Input passed to the "myevent_path" parameter is also not properly verified in myevent.php and viewevent.php before being used to include files. This can be exploited to execute arbitrary PHP code by including PHP files from local or external resources.
Successful exploitation requires that "register_globals" is enabled and "magic_quotes_gpc" is disabled.
Solution:
Edit the source code to ensure that input is properly sanitised.
Provided and/or discovered by:
3) botan
Changelog:
2006-04-19: Updated "Description" section.
2006-04-26: Added CVE references.
2006-08-10: Added CVE reference.
2006-08-18: Added CVE reference.
|
|
|
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.
|
