CVE-2020-29603: MantisBT Insecure Storage Vulnerability in manage_proj_edit_page.php
Summary
CVE-2020-29603: MantisBT Insecure Storage in manage_proj_edit_page.php. Affects mantisbt/mantisbt versions < 2.24.4. Fixed in 2.24.4. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
MantisBT is an open-source issue tracker that provides a user-friendly interface for managing software development projects. It allows users to track bugs, manage projects, and collaborate effectively. However, prior to version 2.24.4, MantisBT had a vulnerability that allowed unprivileged users to access the names of private projects, compromising project confidentiality.
Vulnerability Detail
The vulnerability exists in the manage_proj_edit_page.php file of MantisBT versions before 2.24.4. It allows any logged-in user without proper privileges to retrieve the names of private projects by manipulating the project_id parameter. This could lead to unauthorized access to sensitive project information, potentially exposing confidential data to users who should not have access.
How To Fix
Minimum fixed version
2.24.4
This is the first release that contains the fix.
composer require mantisbt/mantisbt:2.24.4Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a temporary workaround, restrict access to the manage_proj_edit_page.php file by implementing server-side access controls or by ensuring that only authorized users can log in to the MantisBT system.
Conclusion
The CVE-2020-29603 vulnerability in MantisBT allows unprivileged users to access private project names, posing a risk to project confidentiality. It is crucial to update to version 2.24.4 or later to mitigate this risk. Additionally, utilizing tools like Vulert can help monitor for such vulnerabilities in your open-source projects.
See every vulnerability recorded for mantisbt/mantisbt →
FAQ
The vulnerability allows unprivileged users to see the names of private projects, which can lead to unauthorized information disclosure.
You can check your installation by verifying the version of MantisBT you are using. If it is below 2.24.4, it is affected.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just the composer.lock file.
The CVSS score for this vulnerability is 4.3, indicating a moderate level of severity.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
Related vulnerabilities
Recent vulnerabilities recorded for mantisbt/mantisbt.
