Peppermint Ticket Management up to 0.2.4 POST Request download filepath path traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Peppermint Ticket Management up to 0.2.4 and classified as problematic. This affects an unknown part of the file /api/v1/ticket/1/file/download of the component POST Request Handler. The manipulation of the argument filepath results in path traversal. This vulnerability was named CVE-2023-46864. The attack may be performed from remote. There is no available exploit.
Details
A vulnerability classified as problematic has been found in Peppermint Ticket Management up to 0.2.4 (Ticket Tracking Software). Affected is an unknown code of the file /api/v1/ticket/1/file/download of the component POST Request Handler. The manipulation of the argument filepath with an unknown input leads to a path traversal vulnerability. CWE is classifying the issue as CWE-23. The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize sequences such as ".." that can resolve to a location that is outside of that directory. This is going to have an impact on confidentiality. CVE summarizes:
Peppermint Ticket Management through 0.2.4 allows remote attackers to read arbitrary files via a /api/v1/ticket/1/file/download?filepath=../ POST request.
The weakness was presented 10/30/2023. The advisory is shared for download at github.com. This vulnerability is traded as CVE-2023-46864 since 10/29/2023. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1006.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-51030). Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.8VulDB Meta Temp Score: 4.8
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
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: 🔍
Exploiting
Class: Path traversalCWE: CWE-23 / CWE-22
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
10/29/2023 🔍10/30/2023 🔍
10/30/2023 🔍
02/17/2026 🔍
Sources
Advisory: 171Status: Confirmed
CVE: CVE-2023-46864 (🔍)
GCVE (CVE): GCVE-0-2023-46864
GCVE (VulDB): GCVE-100-243828
EUVD: 🔍
Entry
Created: 10/30/2023 07:30Updated: 02/17/2026 17:19
Changes: 10/30/2023 07:30 (40), 11/19/2023 19:03 (1), 11/19/2023 19:12 (11), 02/17/2026 17:19 (16)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.