CVE-2010-4349: Infoleak

Published Jan 3, 2011
·
Updated

admin/upgradeunattended.php in MantisBT before 1.2.4 allows remote attackers to obtain sensitive information via an invalid dbtype parameter, which reveals the installation path in an error message, related to an unsafe call by MantisBT to a function in the ADOdb Library for PHP.

Affected Software

39 affected components
MantisBT mantisbt<=1.2.3
MantisBT mantisbt=0.18.0
MantisBT mantisbt=0.19.0
MantisBT mantisbt=0.19.0-rc1
MantisBT mantisbt=0.19.0a1
MantisBT mantisbt=0.19.0a2
MantisBT mantisbt=0.19.1
MantisBT mantisbt=0.19.2
MantisBT mantisbt=0.19.3
MantisBT mantisbt=0.19.4
MantisBT mantisbt=0.19.5
MantisBT mantisbt=1.0.0
MantisBT mantisbt=1.0.0-rc1
MantisBT mantisbt=1.0.0-rc2
MantisBT mantisbt=1.0.0-rc3
MantisBT mantisbt=1.0.0-rc4
MantisBT mantisbt=1.0.0-rc5
MantisBT mantisbt=1.0.0a1
MantisBT mantisbt=1.0.0a2
MantisBT mantisbt=1.0.0a3
MantisBT mantisbt=1.0.1
MantisBT mantisbt=1.0.2
MantisBT mantisbt=1.0.3
MantisBT mantisbt=1.0.4
MantisBT mantisbt=1.0.5
MantisBT mantisbt=1.0.6
MantisBT mantisbt=1.0.7
MantisBT mantisbt=1.0.8
MantisBT mantisbt=1.1.0
MantisBT mantisbt=1.1.1
MantisBT mantisbt=1.1.2
MantisBT mantisbt=1.1.4
MantisBT mantisbt=1.1.5
MantisBT mantisbt=1.1.6
MantisBT mantisbt=1.1.7
MantisBT mantisbt=1.1.8
MantisBT mantisbt=1.2.0
MantisBT mantisbt=1.2.1
MantisBT mantisbt=1.2.2

Event History

Jan 3, 2011
CVE Published
via MITRE·07:26 PM
Data Sourced
via MITRE·07:26 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2010-4349?

CVE-2010-4349 is classified as a moderate severity vulnerability due to its potential exposure of sensitive information.

2

How do I fix CVE-2010-4349?

To fix CVE-2010-4349, upgrade MantisBT to version 1.2.4 or later, which addresses this vulnerability.

3

What types of information can be exposed due to CVE-2010-4349?

CVE-2010-4349 can expose sensitive information including the installation path of the MantisBT application.

4

Which versions of MantisBT are affected by CVE-2010-4349?

CVE-2010-4349 affects all MantisBT versions prior to 1.2.4.

5

Is there a workaround for CVE-2010-4349 if I cannot upgrade immediately?

While the best solution is to upgrade, you can restrict access to the upgrade_unattended.php script as a temporary workaround to mitigate the risk.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203