SLiMS 8 Akasia 8.3.1 CSRF Protection Mechanism csrf_token cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in SLiMS 8 Akasia 8.3.1. It has been classified as problematic. Impacted is an unknown function of the component CSRF Protection Mechanism. Performing a manipulation of the argument csrf_token as part of Parameter results in cross-site request forgery. This vulnerability is reported as CVE-2018-12659. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability classified as problematic has been found in SLiMS 8 Akasia 8.3.1. This affects an unknown code block of the component CSRF Protection Mechanism. The manipulation of the argument csrf_token as part of a Parameter leads to a cross-site request forgery vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
SLiMS 8 Akasia 8.3.1 allows remote attackers to bypass the CSRF protection mechanism and obtain admin access by omitting the csrf_token parameter.
The bug was discovered 05/21/2018. The weakness was disclosed 06/22/2018 (Website). The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2018-12659 since 06/22/2018. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 32 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 entries VDB-119816, VDB-119815, VDB-119814 and VDB-119813 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.1VulDB Meta Temp Score: 7.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
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: 🔍
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
05/21/2018 🔍06/22/2018 🔍
06/22/2018 🔍
06/22/2018 🔍
06/23/2018 🔍
03/28/2023 🔍
Sources
Advisory: 103Status: Not defined
CVE: CVE-2018-12659 (🔍)
GCVE (CVE): GCVE-0-2018-12659
GCVE (VulDB): GCVE-100-119817
See also: 🔍
Entry
Created: 06/23/2018 08:35Updated: 03/28/2023 16:05
Changes: 06/23/2018 08:35 (59), 02/21/2020 11:41 (1), 03/28/2023 16:05 (3)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.