|
TinyPHPForum Multiple Vulnerabilities
|
|
Secunia Advisory:
|
SA18293
|
|
|
Release Date:
|
2006-01-05
|
|
Last Update:
|
2007-03-02
|
|
Popularity:
|
4,829 views
|
|
|
Critical:
|
Highly critical
|
|
Impact:
|
Security Bypass
Cross Site Scripting
Exposure of system information
Exposure of sensitive information
System access
|
|
Where:
|
From remote
|
|
Solution Status:
|
Unpatched
|
|
| Software: | TinyPHPForum 3.x
|
|
|
Subscribe:
|
Instant alerts on relevant vulnerabilities 
|
|
| CVE reference: | CVE-2006-1898
CVE-2006-0102
CVE-2006-0103
CVE-2006-0104
CVE-2006-7063
|
|
Description:
Some vulnerabilities and a security issue have been reported in TinyPHPForum, which can be exploited by malicious people to conduct cross-site scripting and script insertion attacks, bypass certain security restrictions, disclose sensitive information, and compromise a vulnerable system.
1) Input passed to the URL of a link when posting a message isn't properly verified before being used. This can be exploited to inject arbitrary JavaScript code, which will be executed in a user's browser session in context of an affected site when a link with the "javascript:" URI handler is followed in a malicious message.
2) The problem is that user credentials are stored insecurely in the "users" directory inside the web root. This can be exploited to disclose users' encrypted passwords and other information.
3) Input passed to the "uname" parameter in "profile.php" when viewing a profile isn't properly sanitised before being used to view user content. This can be exploited to disclose the content of arbitrary files via directory traversal attacks.
Successful exploitation requires that "magic_quotes_gpc" is disabled.
4) Input passed to the "uname" parameter in "profile.php" and "error.php", the "query" parameter in search.php, and the "siteName", "title", and "style" parameters in header.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.
Some other parameters when creating new users and topics may also be affected.
5) Input passed to the "fid" parameter in action.php and the "f" parameter in split.php isn't properly sanitised before being used to create files. This can be exploited to create a malicious PHP script inside the web root.
6) Input passed via the "a" and "img" BBcode tags when posting 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.
7) The problem is that it is possible to gain administrative privileges by setting the "makeadmin" parameter to "true" when updating the profile via updatepf.php.
The vulnerabilities and the security issue have been reported in version 3.6. Other versions may also be affected.
Solution:
Use another product.
Provided and/or discovered by:
1-3) Aliaksandr Hartsuyeu
4) Hessam M.Salehi, Iran Hackerz Security Team
Additional information provided by Sirdarckcat.
5-7) Sirdarckcat
Changelog:
2006-04-18: Added additional vulnerabilities provided by Hessam M.Salehi.
2006-04-27: Added CVE reference.
2006-08-01: Added additional vulnerabilities provided by Sirdarckcat. Updated "Solution" section.
2006-08-04: Added CVE references.
2007-03-02: Added CVE reference.
Original Advisory:
1-3) http://evuln.com/vulns/14/summary.html
4-7) http://lists.grok.org.uk/pipermail/full-disclosure/2006-July/048316.html
|
|
|
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.
|
