What is the severity of CVE-2018-9839?

The severity of CVE-2018-9839 is medium, with a severity score of 6.5.

How can an attacker exploit CVE-2018-9839?

An attacker can exploit CVE-2018-9839 by using a crafted request on bug_report_page.php to modify the 'm_id' parameter and view private issue details.

Which versions of MantisBT are affected by CVE-2018-9839?

MantisBT versions 1.3.14 and 2.0.0 are affected by CVE-2018-9839.

How can I fix CVE-2018-9839?

To fix CVE-2018-9839, you should upgrade MantisBT to a version higher than 2.0.0 or apply the necessary patches provided by the vendor.

Vulnerability/
CVE-2018-9839

medium

6.5

CWE

6/6/2019

5/8/2024

CVE-2018-9839: Input Validation

Q: Where can I find more information about CVE-2018-9839?

More information about CVE-2018-9839 can be found in the references: https://github.com/mantisbt/mantisbt/commit/1fbcd9bca2f2c77cb61624d36ddee4b3802c38ea and https://mantisbt.org/bugs/view.php?id=24221.

First published: Thu Jun 06 2019(Updated: )

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).

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Mantisbt Mantisbt	<=1.3.14
Mantisbt Mantisbt	=2.0.0

Remedy

https://github.com/mantisbt/mantisbt/commit/1fbcd9bca2f2c77cb61624d36ddee4b3802c38ea

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2018-9839?
The severity of CVE-2018-9839 is medium, with a severity score of 6.5.
How can an attacker exploit CVE-2018-9839?
An attacker can exploit CVE-2018-9839 by using a crafted request on bug_report_page.php to modify the 'm_id' parameter and view private issue details.
Which versions of MantisBT are affected by CVE-2018-9839?
MantisBT versions 1.3.14 and 2.0.0 are affected by CVE-2018-9839.
How can I fix CVE-2018-9839?
To fix CVE-2018-9839, you should upgrade MantisBT to a version higher than 2.0.0 or apply the necessary patches provided by the vendor.
Where can I find more information about CVE-2018-9839?
More information about CVE-2018-9839 can be found in the references: https://github.com/mantisbt/mantisbt/commit/1fbcd9bca2f2c77cb61624d36ddee4b3802c38ea and https://mantisbt.org/bugs/view.php?id=24221.

collector/nvd-index
agent/severity
agent/weakness
agent/references
agent/author
agent/type
agent/tags
agent/event
agent/description
agent/remedy
agent/last-modified-date
agent/softwarecombine
agent/first-publish-date
collector/mitre-cve
source/MITRE
vendor/mantisbt
canonical/mantisbt mantisbt
version/mantisbt mantisbt/1.3.14
version/mantisbt mantisbt/2.0.0

Company

Resources

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.