CVE-2003-0499: Low severity Mantis Mantis vulnerability
Mantis 0.17.5 and earlier stores its database password in cleartext in a world-readable configuration file, which allows local users to perform unauthorized database operations.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
Remove world-read permission on the Mantis configuration file that contains the database password so it is not world-readable. Ensure the file is readable only by the application/service account and administrators (for example, run: chmod 640 /path/to/mantis/config_inc.php or chmod 600 /path/to/mantis/config_inc.php and verify with ls -l).
Mantis (debian/mantis) configuration file that stores the database password file permissions (world-readable) = remove world-readable bit (e.g., chmod 640 or chmod 600) - Operational
Rotate the database credentials that were stored in the world-readable configuration file: create a new database password, update the Mantis configuration with the new password, and restart the Mantis service (and any associated web service) to apply the change. Verify application connectivity to the database and revoke the old credentials.
Event History
Frequently Asked Questions
What is the severity of CVE-2003-0499?
CVE-2003-0499 is classified as a medium severity vulnerability due to the exposure of sensitive database credentials.
How do I fix CVE-2003-0499?
To fix CVE-2003-0499, update to Mantis version 0.18.0 or later, which addresses the cleartext password issue.
What versions of Mantis are affected by CVE-2003-0499?
Mantis versions 0.17.5 and earlier are affected by CVE-2003-0499.
What impact can CVE-2003-0499 have on a system?
CVE-2003-0499 allows local users to access the database and perform unauthorized operations due to cleartext password storage.
Is there a workaround for CVE-2003-0499?
A potential workaround for CVE-2003-0499 is to restrict access to the configuration file containing the database password.