Open Ticket Request System up to 5.0.33/6.0.15/7.0.3 PictureUpload.pm Content-Type code injection
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
6.1 | $0-$5k | 0.00 |
A vulnerability was found in Open Ticket Request System up to 5.0.33/6.0.15/7.0.3 (Ticket Tracking Software). It has been classified as problematic. Affected is an unknown function of the file Kernel/Modules/PictureUpload.pm. The manipulation of the argument Content-Type
with an unknown input leads to a code injection vulnerability. CWE is classifying the issue as CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. This is going to have an impact on integrity. CVE summarizes:
An issue was discovered in Open Ticket Request System (OTRS) 5.x before 5.0.34, 6.x before 6.0.16, and 7.x before 7.0.4. An attacker who is logged into OTRS as an agent or a customer user may upload a carefully crafted resource in order to cause execution of JavaScript in the context of OTRS. This is related to Content-type mishandling in Kernel/Modules/PictureUpload.pm.
The bug was discovered 01/18/2019. The weakness was disclosed 03/13/2019 (Website). The advisory is shared for download at lists.debian.org. This vulnerability is traded as CVE-2019-9752 since 03/13/2019. It is possible to launch the attack remotely. The successful exploitation requires a authentication. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1059.
The vulnerability was handled as a non-public zero-day exploit for at least 54 days. During that time the estimated underground price was around $0-$5k. The commercial vulnerability scanner Qualys is able to test this issue with plugin 176647 (Debian Security Update for otrs2 (DLA 1721-1)).
Upgrading to version 5.0.34, 6.0.16 or 7.0.4 eliminates this vulnerability.
The entry 131711 is pretty similar.
Product
Type
Name
Version
- 5.0.0
- 5.0.1
- 5.0.2
- 5.0.3
- 5.0.4
- 5.0.5
- 5.0.6
- 5.0.7
- 5.0.8
- 5.0.9
- 5.0.10
- 5.0.11
- 5.0.12
- 5.0.13
- 5.0.14
- 5.0.15
- 5.0.16
- 5.0.17
- 5.0.18
- 5.0.19
- 5.0.20
- 5.0.21
- 5.0.22
- 5.0.23
- 5.0.24
- 5.0.25
- 5.0.26
- 5.0.27
- 5.0.28
- 5.0.29
- 5.0.30
- 5.0.31
- 5.0.32
- 5.0.33
- 6.0.0
- 6.0.1
- 6.0.2
- 6.0.3
- 6.0.4
- 6.0.5
- 6.0.6
- 6.0.7
- 6.0.8
- 6.0.9
- 6.0.10
- 6.0.11
- 6.0.12
- 6.0.13
- 6.0.14
- 6.0.15
- 7.0.0
- 7.0.1
- 7.0.2
- 7.0.3
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB CVSS-B Score: 🔍VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.1VulDB Meta Temp Score: 6.1
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
CVSSv2
AV | AC | Au | C | I | A |
---|---|---|---|---|---|
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
---|---|---|---|---|---|
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Code injectionCWE: CWE-94 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
0-Day | unlock | unlock | unlock | unlock |
---|---|---|---|---|
Today | unlock | unlock | unlock | unlock |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Open Ticket Request System 5.0.34/6.0.16/7.0.4
Timeline
01/18/2019 🔍03/13/2019 🔍
03/13/2019 🔍
03/14/2019 🔍
08/01/2023 🔍
Sources
Advisory: DLA 1721-1Status: Not defined
CVE: CVE-2019-9752 (🔍)
See also: 🔍
Entry
Created: 03/14/2019 08:29Updated: 08/01/2023 10:30
Changes: 03/14/2019 08:29 (60), 05/16/2020 14:49 (2), 08/01/2023 10:30 (4)
Complete: 🔍
No comments yet. Languages: en.
Please log in to comment.