Secunia Security Advisory - Some weaknesses and vulnerabilities have been discovered in TorrentTrader Classic, which can be exploited by malicious users to conduct script-insertion and SQL injection attacks, and by malicious people to disclose potentially sensitive information, bypass certain security restrictions, and conduct cross-site scripting and SQL injection attacks.
7ab5bf9498a0f5590c7b9f2993163fb215c967fe407b2e8259cec0ee5409593b
----------------------------------------------------------------------
Do you have VARM strategy implemented?
(Vulnerability Assessment Remediation Management)
If not, then implement it through the most reliable vulnerability
intelligence source on the market.
Implement it through Secunia.
For more information visit:
http://secunia.com/advisories/business_solutions/
Alternatively request a call from a Secunia representative today to
discuss how we can help you with our capabilities contact us at:
sales@secunia.com
----------------------------------------------------------------------
TITLE:
TorrentTrader Classic Multiple Vulnerabilities
SECUNIA ADVISORY ID:
SA35456
VERIFY ADVISORY:
http://secunia.com/advisories/35456/
DESCRIPTION:
Some weaknesses and vulnerabilities have been discovered in
TorrentTrader Classic, which can be exploited by malicious users to
conduct script-insertion and SQL injection attacks, and by malicious
people to disclose potentially sensitive information, bypass certain
security restrictions, and conduct cross-site scripting and SQL
injection attacks.
1) Input passed to the "origmsg" parameter in account-inbox.php when
deleting a message 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 requires valid user credentials.
2) Access to the "backup-database.php" script is not properly
restricted. Additionally, the script creates database dumps with an
easy to guess filename inside a publicly accessible folder, which can
be exploited to e.g. create and download database dumps.
3) Input passed to the "wherecatin" parameter in browse.php is not
properly sanitised before being used in SQL queries. This can be
exploited to manipulate SQL queries by injecting arbitrary SQL code.
4) Access to the "check.php" and "phpinfo.php" scripts is not
properly restricted, which can be exploited to disclose certain
system information (e.g. system paths, PHP settings, and certain file
permission settings).
5) Input passed to the "categ" parameter in delreq.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 requires privileges to delete requests.
6) Input passed to the "choice" parameter in 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 requires valid user credentials.
7) Input passed to the "id" parameter in modrules.php (if "act" is
set to "edit") 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 requires moderator privileges.
8) Input passed to the "user", "torrent", "forumid", and "forumpost"
POST parameters in report.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 requires valid user credentials.
9) Input passed to the "delreport[]" parameter in takedelreport.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 requires moderator privileges.
10) Input passed to the "delreq[]" parameter in takedelreq.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 requires valid user credentials.
11) Input passed to the "warndisable[]" parameter in
takewarndisable.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 requires moderator privileges.
12) Input passed to the "limit" parameter in today.php is not
properly sanitised before being used in SQL queries. This can be
exploited to manipulate SQL queries by injecting arbitrary SQL code.
13) Input passed to the "where" parameter in torrents-details.php is
not properly sanitised before being used in SQL queries. This can be
exploited to manipulate SQL queries by injecting arbitrary SQL code.
14) Input passed to the "categ" parameter in admin-delreq.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 requires moderator privileges.
15) Input passed via the "Title" field when requesting a torrent and
to the "Torrent Name" field when uploading a torrent is not properly
sanitised before being used. This can be exploited to insert
arbitrary HTML and script code, which will be executed in a user's
browser session in context of an affected site when the malicious
data is viewed.
Successful exploitation requires valid user privileges.
16) The application does not properly restrict access to the
"backend/admin-functions.php" script, which can be exploited on a
case insensitive file system (e.g. Windows) to bypass the access
restrictions.
Note: This may further be exploited to e.g. include arbitrary local
files.
17) Input passed to the "ttversion" parameter in
themes/default/footer.php, the "SITENAME" and "CURUSER" parameters in
themes/default/header.php, the "todayactive" parameter in
visitorstoday.php, the "activepeople" parameter in visitorsnow.php,
and the "faq_categ[][title]" parameter in faq.php 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.
The vulnerabilities are confirmed in version 1.09. Other versions may
also be affected.
SOLUTION:
Edit the source code to ensure that input is properly sanitised and
verified and restricted access to insufficiently restricted scripts
(e.g. via ".htaccess").
PROVIDED AND/OR DISCOVERED BY:
Janek Vind a.k.a. waraxe
ORIGINAL ADVISORY:
http://www.waraxe.us/advisory-74.html
----------------------------------------------------------------------
About:
This Advisory was delivered by Secunia as a free service to help
everybody keeping their systems up to date against the latest
vulnerabilities.
Subscribe:
http://secunia.com/advisories/secunia_security_advisories/
Definitions: (Criticality, Where etc.)
http://secunia.com/advisories/about_secunia_advisories/
Please Note:
Secunia recommends that you verify all advisories you receive by
clicking the link.
Secunia NEVER sends attached files with advisories.
Secunia does not advise people to install third party patches, only
use those supplied by the vendor.
----------------------------------------------------------------------