DSA-153-1 mantis -- cross site code execution and privilege escalation

Related Vulnerabilities: CVE-2002-1114   CVE-2002-1113   CVE-2002-1112   CVE-2002-1111   CVE-2002-1110  

Joao Gouveia discovered an uninitialized variable which was insecurely used with file inclusions in the mantis package, a php based bug tracking system. The Debian Security Team found even more similar problems. When these occasions are exploited, a remote user is able to execute arbitrary code under the webserver user id on the web server hosting the mantis system. Jeroen Latour discovered that Mantis did not check all user input, especially if they do not come directly from form fields. This opens up a wide variety of SQL poisoning vulnerabilities on systems without magic_quotes_gpc enabled. Most of these vulnerabilities are only exploitable in a limited manner, since it is no longer possible to execute multiple queries using one call to mysql_query(). There is one query which can be tricked into changing an account's access level. Jeroen Latour also reported that it is possible to instruct Mantis to show reporters only the bugs that they reported, by setting the limit_reporters option to ON. However, when formatting the output suitable for printing, the program did not check the limit_reporters option and thus allowed reporters to see the summaries of bugs they did not report. Jeroen Latour discovered that the page responsible for displaying a list of bugs in a particular project, did not check whether the user actually has access to the project, which is transmitted by a cookie variable. It accidentally trusted the fact that only projects accessible to the user were listed in the drop-down menu. This provides a malicious user with an opportunity to display the bugs of a private project selected. These problems have been fixed in version 0.17.1-2.2 for the current stable distribution (woody) and in version 0.17.4a-2 for the unstable distribution (sid). The old stable distribution (potato) is not affected, since it doesn't contain the mantis package. Additional information: Mantis Advisory/2002-01 Mantis Advisory/2002-02 Mantis Advisory/2002-03 Mantis Advisory/2002-04 Mantis Advisory/2002-05 We recommend that you upgrade your mantis packages immediately.

Debian Security Advisory

DSA-153-1 mantis -- cross site code execution and privilege escalation

Date Reported:
14 Aug 2002
Affected Packages:
mantis
Vulnerable:
Yes
Security database references:
In the Bugtraq database (at SecurityFocus): BugTraq ID 5565, BugTraq ID 5563, BugTraq ID 5509, BugTraq ID 5504, BugTraq ID 5514, BugTraq ID 5515, BugTraq ID 5510.
In Mitre's CVE dictionary: CVE-2002-1114, CVE-2002-1113, CVE-2002-1112, CVE-2002-1111, CVE-2002-1110.
More information:

Joao Gouveia discovered an uninitialized variable which was insecurely used with file inclusions in the mantis package, a php based bug tracking system. The Debian Security Team found even more similar problems. When these occasions are exploited, a remote user is able to execute arbitrary code under the webserver user id on the web server hosting the mantis system.

Jeroen Latour discovered that Mantis did not check all user input, especially if they do not come directly from form fields. This opens up a wide variety of SQL poisoning vulnerabilities on systems without magic_quotes_gpc enabled. Most of these vulnerabilities are only exploitable in a limited manner, since it is no longer possible to execute multiple queries using one call to mysql_query(). There is one query which can be tricked into changing an account's access level.

Jeroen Latour also reported that it is possible to instruct Mantis to show reporters only the bugs that they reported, by setting the limit_reporters option to ON. However, when formatting the output suitable for printing, the program did not check the limit_reporters option and thus allowed reporters to see the summaries of bugs they did not report.

Jeroen Latour discovered that the page responsible for displaying a list of bugs in a particular project, did not check whether the user actually has access to the project, which is transmitted by a cookie variable. It accidentally trusted the fact that only projects accessible to the user were listed in the drop-down menu. This provides a malicious user with an opportunity to display the bugs of a private project selected.

These problems have been fixed in version 0.17.1-2.2 for the current stable distribution (woody) and in version 0.17.4a-2 for the unstable distribution (sid). The old stable distribution (potato) is not affected, since it doesn't contain the mantis package.

Additional information:

We recommend that you upgrade your mantis packages immediately.

Fixed in:

Debian GNU/Linux 3.0 (woody)

Source:
http://security.debian.org/pool/updates/main/m/mantis/mantis_0.17.1-2.2.dsc
http://security.debian.org/pool/updates/main/m/mantis/mantis_0.17.1-2.2.diff.gz
http://security.debian.org/pool/updates/main/m/mantis/mantis_0.17.1.orig.tar.gz
Architecture-independent component:
http://security.debian.org/pool/updates/main/m/mantis/mantis_0.17.1-2.2_all.deb

MD5 checksums of the listed files are available in the original advisory.