Skip to content

GHSA-hf4x-6h87-hm79 CVE-2023-22476

MantisBT may expose private issues' summaries to unauthorized users

Medium Packagist
Severity
4.3 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.61%
Chance of exploitation in the next 30 days. Higher than 49.09% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
Fix
2.25.6
Upgrade mantisbt/mantisbt to this version or later

Description

Impact

Due to insufficient access-level checks, any logged-in user allowed to perform Group Actions can get access to the Summary field of private Issues (i.e. having Private view status, or belonging to a private Project) via a crafted bug_arr[] parameter in bug_actiongroup_ext.php.

Patches

The vulnerability has been fixed in MantisBT version 2.25.6.

Workarounds

None

Credits

Thanks to d3vpoo1 for reporting the issue.

References

Affected versions

Packagist

PackageVulnerableFixed in
mantisbt/mantisbt
< 2.25.6
2.25.6

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

mantisbt/mantisbt Packagist → 2.25.6

composer
composer require mantisbt/mantisbt:^2.25.6

Severity breakdown

CVSS 3.1 4.3

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Weakness

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

How to prevent it
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-h2wf-967x-gxvw
MantisBT: Stored XSS in print_all_bug_page_word.php
High Also affects mantisbt/mantisbt
GHSA-4vpf-w7qv-5h3q
MantisBT: Injection of TIME_TRACKING and REMINDER Notes via REST and SOAP APIs
Medium Also affects mantisbt/mantisbt
GHSA-3v2j-6fw9-f57c
MantisBT: REST and SOAP API Issue Update Accepts Unreleased Product Versions From Updaters
Medium Also affects mantisbt/mantisbt
GHSA-vcrw-4xvv-jh49
MantisBT: Reflected XSS in admin/install.php via unescaped printf
Critical Also affects mantisbt/mantisbt
GHSA-77x8-3v3h-hrhv
MantisBT: Reflected XSS in admin/install.php
Critical Also affects mantisbt/mantisbt
GHSA-m7ph-9558-mrx3
MantisBT: REST API unauthorized Issue status change
Medium Also affects mantisbt/mantisbt
GHSA-v84x-qvhg-f36r
MantisBT: Remote Code Execution via eval() Class Hoisting in adm_config_set.php
High Also affects mantisbt/mantisbt
GHSA-c2xg-qjqw-2v98
MantisBT: SOAP API Authentication Bypass with Privilege Escalation to Administrator
Critical Also affects mantisbt/mantisbt
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor