Missing X-Content-Type-Options: nosniff Header Allows MIME Type Sniffing
OTRS AG OTRS · OTRS AG ((OTRS)) Community Edition
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| OTRS AG OTRS |
| No fix yet |
| OTRS AG ((OTRS)) Community Edition |
| No fix yet |
OTRS AG OTRS · OTRS AG ((OTRS)) Community Edition
| Product | Affected | Fixed in |
|---|---|---|
| OTRS AG OTRS |
| No fix yet |
| OTRS AG ((OTRS)) Community Edition |
| No fix yet |
A vulnerability exists in OTRS and ((OTRS Community Edition)) that fail to set the HTTP response header X-Content-Type-Options to nosniff. An attacker could exploit this vulnerability by uploading or inserting content that would be treated as a different MIME type than intended.
This issue affects:
* OTRS 7.0.X
* OTRS 8.0.X * OTRS 2023.X * OTRS 2024.X
* ((OTRS)) Community Edition: 6.0.x
Products based on the ((OTRS)) Community Edition also very likely to be affected
From the CVE record · OTRS
OTRS and ((OTRS)) Community Edition do not set the X-Content-Type-Options: nosniff HTTP response header. An attacker who can upload or insert content could have it treated as a different MIME type than intended. The input does not specify whether authentication or user interaction is required.
Operators of OTRS 7.0.X, 8.0.X, 2023.X or 2024.X, and ((OTRS)) Community Edition 6.0.x should check; products based on the Community Edition may also be affected.