Bug 663230 (CVE-2010-4348, CVE-2010-4349, CVE-2010-4350)
Summary: | CVE-2010-4348 CVE-2010-4349 CVE-2010-4350 MantisBT <1.2.4 multiple vulnerabilities (LFI, XSS and PD) | ||
---|---|---|---|
Product: | [Other] Security Response | Reporter: | David Hicks <d> |
Component: | vulnerability | Assignee: | Red Hat Product Security <security-response-team> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | unspecified | CC: | giallu, jlieskov, jrusnack |
Target Milestone: | --- | Keywords: | Security |
Target Release: | --- | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://www.mantisbt.org/bugs/view.php?id=12607 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-02-21 23:23:55 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 663299 | ||
Bug Blocks: |
Description
David Hicks
2010-12-15 03:19:40 UTC
(In reply to comment #0) Hi David, thank you for such a complete report. > > I have requested CVE numbers via oss-sec (awaiting list moderation). Looks like the CVE identifiers request did not made it to oss-security yet. To Gianluca: We will update this bug with CVE identifiers later, once they are assigned to the issues. Could you please schedule Fedora MantisBT updates with the patch below? (Fedora bug will follow shortly) > > As Redhat is using MantisBT 1.1.x you will need to apply the following > patch to resolve the issue in this older version of MantisBT: > http://git.mantisbt.org/?p=mantisbt.git;a=commitdiff_plain;h=2641fdc60d2032ae1586338d6416e1eadabd7590 Thanks && Regards, Jan. -- Jan iankko Lieskovsky / Red Hat Security Response Team These issues affect the versions of the mantis package, as shipped with Fedora release of 13 and 14. These issues affect the version of the mantis package, as present within EPEL-5 repository. Please schedule an update (patch is above). Public PoCs (from http://www.mantisbt.org/bugs/view.php?id=12607): 1), cross-site scripting (XSS): http://[mantis_root_host]/admin/upgrade_unattended.php?db_type=%3Cscript%3Ealert%281%29%3C/script%3E 2), local file inclusion (LFI): http://[mantis_root_host]/admin/upgrade_unattended.php?db_type=..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2fboot.ini%00 3), path disclosure (PD): http://[mantis_root_host]/admin/upgrade_unattended.php?db_type=%27 Created mantis tracking bugs for this issue Affects: fedora-all [bug 663299] I guess it's relevant to note the default apache configuration provided with the mantis package includes the following. # Admin directory access is disabled by default; do not change this unless # you are performing the first installation or a database schema update. # See README.Fedora for more details <Directory /usr/share/mantis/admin> Order Deny,Allow Deny from All Allow from None </Directory> Thanks Jan & Gianluca. Debian (and by extension Ubuntu) use the same Apache configuration to help protect the /admin/ directory. As a result they have decided that the severity of the bug is not as high as first anticipated by upstream. I guess it comes down to whether a typical user of this package will keep the /admin/ directory permissions in a locked down state. This issue is more of a concern for Gentoo (and MantisBT users using the upstream package) where the /admin/ directory permissions are not in place. From Josh Bressers (oss-sec mailing list): CVE-2010-4348: Cross site scripting CVE-2010-4349: Path disclosure CVE-2010-4350: Local file inclusion Gianluca, David, thank you for the comments: https://bugzilla.redhat.com/show_bug.cgi?id=663230#c5 https://bugzilla.redhat.com/show_bug.cgi?id=663230#c6 (In reply to comment #5) > I guess it's relevant to note the default apache configuration provided with > the mantis package includes the following. > > > # Admin directory access is disabled by default; do not change this unless > # you are performing the first installation or a database schema update. > # See README.Fedora for more details Based on the above comments decreased severity of the issues to moderate. But we should still address them (to sanitize / protect also not so likely configurations). This was fixed in 1.1.8-5 |