Vaultize Enterprise File Sharing 17.05.31 History vaultize_session_id improper authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Vaultize Enterprise File Sharing 17.05.31 and classified as critical. Impacted is an unknown function of the component History Handler. Executing a manipulation of the argument vaultize_session_id as part of Cookie can lead to improper authorization. This vulnerability is registered as CVE-2018-10211. It is possible to launch the attack remotely. No exploit is available.
Details
A vulnerability classified as critical was found in Vaultize Enterprise File Sharing 17.05.31. This vulnerability affects an unknown code of the component History Handler. The manipulation of the argument vaultize_session_id as part of a Cookie leads to a improper authorization vulnerability. The CWE definition for the vulnerability is CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
An issue was discovered in Vaultize Enterprise File Sharing 17.05.31. There is improper authorization when listing the history of another user via a modified "vaultize_session_id" value in a cookie.
The bug was discovered 04/18/2018. The weakness was published 04/25/2018 (Website). The advisory is shared for download at excellium-services.com. This vulnerability was named CVE-2018-10211 since 04/19/2018. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1548.002.
The vulnerability was handled as a non-public zero-day exploit for at least 7 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.
Similar entries are available at VDB-117102, VDB-117101, VDB-117099 and VDB-117098. Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.3
VulDB Base Score: 7.3
VulDB Temp Score: 7.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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Improper authorizationCWE: CWE-285 / CWE-266
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
04/18/2018 🔍04/19/2018 🔍
04/25/2018 🔍
04/25/2018 🔍
04/26/2018 🔍
05/30/2025 🔍
Sources
Advisory: excellium-services.comStatus: Not defined
CVE: CVE-2018-10211 (🔍)
GCVE (CVE): GCVE-0-2018-10211
GCVE (VulDB): GCVE-100-117100
See also: 🔍
Entry
Created: 04/26/2018 08:54Updated: 05/30/2025 18:49
Changes: 04/26/2018 08:54 (59), 01/31/2020 15:54 (1), 05/30/2025 18:49 (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.