Bug 800665 (CVE-2012-1118, CVE-2012-1119, CVE-2012-1120, CVE-2012-1121, CVE-2012-1122, CVE-2012-1123)

Summary: CVE-2012-1118 CVE-2012-1119 CVE-2012-1120 CVE-2012-1121 CVE-2012-1122 CVE-2012-1123 mantis: multiple flaws fixed in 1.2.9
Product: [Other] Security Response Reporter: Vincent Danen <vdanen>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: extras-orphan, giallu, guillaume, sven
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: impact=important,public=20120304,reported=20120306,source=oss-security,cvss2=5.8/AV:N/AC:M/Au:N/C:P/I:P/A:N,fedora-all/mantis=affected,epel-5/mantis=affected
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-15 04:16:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On: 800666, 800667    
Bug Blocks:    

Description Vincent Danen 2012-03-06 21:54:08 UTC
MantisBT 1.2.9 [1],[2] fixes the following flaws:

MantisBT < 1.2.9 array value for $g_private_bug_threshold configuration option allows bypass of access checks (CVE-2012-1118)

MantisBT < 1.2.9 copy/clone bug report action failed to leave an audit trail (CVE-2012-1119)

MantisBT < 1.2.9 delete_bug_threshold/bugnote_allow_user_edit_delete access check bypass via SOAP API (CVE-2012-1120)

MantisBT < 1.2.9 managers of specific projects could update global category settings (CVE-2012-1121)

MantisBT < 1.2.9 incorrect access checks performed when moving bugs between projects (CVE-2012-1122)

MantisBT < 1.2.9 SOAP API null password authentication bypass (CVE-2012-1123)

[1] http://www.mantisbt.org/blog/?p=156
[2] http://www.openwall.com/lists/oss-security/2012/03/06/6

NOTE: I don't currently know if these issues affect 1.1.8 (as shipped with EPEL5), but am filing a tracking bug for it regardless (that version is quite old, so it may or not be affected by these issues; I've not had the time to dig into it further to see what may affect it or not).

Comment 1 Vincent Danen 2012-03-06 21:56:10 UTC
Created mantis tracking bugs for this issue

Affects: fedora-all [bug 800666]
Affects: epel-5 [bug 800667]

Comment 2 Fedora Update System 2012-11-23 07:56:06 UTC
mantis-1.2.12-1.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 3 Fedora Update System 2012-11-24 03:24:24 UTC
mantis-1.2.12-1.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 4 Fedora Update System 2012-11-24 03:25:26 UTC
mantis-1.2.12-1.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 5 Vincent Danen 2013-03-15 04:16:25 UTC
EPEL5 hasn't been touched since Dec 2010, and the package is technically orphaned.  As a result I'm closing this bug as this issue is fixed in Fedora.  The EPEL5 tracking bug #800667 will remain open until either mantis is dropped from EPEL or it is fixed.