JS Support Ticket 1.1.0 on Joomla cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in JS Support Ticket 1.1.0 on Joomla. The affected element is an unknown function of the component Ticket Handler. The manipulation leads to cross-site request forgery. This vulnerability is listed as CVE-2018-6007. The attack may be initiated remotely. In addition, an exploit is available. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Details
A vulnerability was found in JS Support Ticket 1.1.0 on Joomla (Ticket Tracking Software) and classified as problematic. This issue affects an unknown code of the component Ticket Handler. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. Using CWE to declare the problem leads to CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. Impacted is integrity. The summary by CVE is:
CSRF exists in the JS Support Ticket 1.1.0 component for Joomla! and allows attackers to inject HTML or edit a ticket.
The bug was discovered 01/27/2018. The weakness was presented 01/29/2018 as File 146135/Joo (Packetstorm). The advisory is shared at packetstormsecurity.com. The identification of this vulnerability is CVE-2018-6007 since 01/22/2018. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details are unknown but a public exploit is available.
The exploit is available at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 2 days. During that time the estimated underground price was around $0-$5k.
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 Exploit-DB (43912). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.6VulDB Meta Temp Score: 6.4
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
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: Cross-site request forgeryCWE: CWE-352 / CWE-862 / CWE-863
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/22/2018 🔍01/27/2018 🔍
01/29/2018 🔍
01/29/2018 🔍
01/29/2018 🔍
07/03/2024 🔍
Sources
Advisory: File 146135/JooStatus: Confirmed
CVE: CVE-2018-6007 (🔍)
GCVE (CVE): GCVE-0-2018-6007
GCVE (VulDB): GCVE-100-112613
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 01/29/2018 09:13 AMUpdated: 07/03/2024 07:15 PM
Changes: 01/29/2018 09:13 AM (59), 06/26/2020 06:57 PM (4), 07/03/2024 07:15 PM (16)
Complete: 🔍
Cache ID: 244:785:40
No comments yet. Languages: en.
Please log in to comment.