CVE-2018-9839
Last modified
CVE-2018-9839 is a vulnerability of currently unknown severity. An issue was discovered in MantisBT through 1.3.14, and 2.0.0. Using a crafted request on bug_report_page.php (modifying the 'm_id' parameter), any user with REPORTER access or above is able to view any private issue's details (summary, description, steps to reproduce, additional information) when cloning it. EPSS estimates a 1.24% chance of exploitation in the next 30 days.
Description
An issue was discovered in MantisBT through 1.3.14, and 2.0.0. Using a crafted request on bug_report_page.php (modifying the 'm_id' parameter), any user with REPORTER access or above is able to view any private issue's details (summary, description, steps to reproduce, additional information) when cloning it. By checking the 'Copy issue notes' and 'Copy attachments' checkboxes and completing the clone operation, this data also becomes public (except private notes).
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Mantisbt | Mantisbt | <= 1.3.14 |
| Mantisbt | Mantisbt | 2.0.0 |
References
- https://github.com/mantisbt/mantisbt/commit/1fbcd9bca2f2c77cb61624d36ddee4b3802c38eaPatch, Third Party Advisory
- https://mantisbt.org/bugs/view.php?id=24221Exploit, Issue Tracking, Third Party Advisory
- https://github.com/mantisbt/mantisbt/commit/1fbcd9bca2f2c77cb61624d36ddee4b3802c38eaPatch, Third Party Advisory
- https://mantisbt.org/bugs/view.php?id=24221Exploit, Issue Tracking, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2018-9839?
How severe is CVE-2018-9839?
How do I fix CVE-2018-9839?
Are you affected by CVE-2018-9839?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
