MantisBT before 1.2.12 does not use an expected default value during decisions about whether a user may modify the status of a bug, which allows remote authenticated users to bypass intended access restrictions and make status changes by leveraging a blank value for a per-status setting.

According to its version number, the MantisBT install hosted on the remote web server is affected by multiple vulnerabilities :

  - The application is affected by an information     disclosure vulnerability due to a flaw in using default     values to determine if a user has sufficient privileges     to modify the status of a bug.  This could allow an     unauthenticated, remote attacker to modify the status     of a bug. (CVE-2012-5522)

  - The application is affected by an information     disclosure vulnerability because permissions are     maintained when cloning and transferring an issue to     another project.  This could allow a remote attacker     to view the notes of a cloned issue provided they had     sufficient privileges to view the notes of the original     issue. (CVE-2012-5523)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

New upstream release, fixes several security bugs

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

ID	Name	Product	Family	Severity
64561	MantisBT < 1.2.12 Multiple Vulnerabilities	Nessus	CGI abuses	medium
63039	Fedora 16 : mantis-1.2.12-1.fc16 (2012-18299)	Nessus	Fedora Local Security Checks	high
63038	Fedora 17 : mantis-1.2.12-1.fc17 (2012-18294)	Nessus	Fedora Local Security Checks	high
63036	Fedora 18 : mantis-1.2.12-1.fc18 (2012-18273)	Nessus	Fedora Local Security Checks	high

Detections

Analytics

CVE-2012-5522

medium

Tenable Plugins

medium

high

high

high