MantisBT has a Content Security Policy bypass via attachments
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| mantisbt | mantisbt | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Mantisbt | Mantisbt |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-9c3j-xm6v-j7j3 | MantisBT has a Content Security Policy bypass via attachments |
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.498% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Mantisbt
Mantisbt mantisbt |
|
| Vendors & Products |
Mantisbt
Mantisbt mantisbt |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Mantis Bug Tracker (MantisBT) is an open source issue tracker. In versions 2.28.1 and below, given any pre-existing XSS / HTML injection vulnerability, an attacker can bypass the Content Security Policy's script-src directive by uploading a crafted attachment to any issue that, when accessed via the file_download.php link, will be downloaded with a valid JavaScript MIME type resulting in script execution. The uploaded payload must be sniffed as a valid JavaScript MIME type by PHP finfo (see file_create_finfo() API function). Non-JavaScript MIME types will not get imported in a <script> tag by the browser, due to response header X-Content-Type-Options being set to nosniff, which requires all imported JavaScript files to be a valid JavaScript MIME type. This issue has been fixed in version 2.28.2. | |
| Title | MantisBT has a Content Security Policy bypass via attachments | |
| Weaknesses | CWE-358 CWE-79 |
|
| References |
| |
| Metrics |
cvssV4_0
|