| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.7 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in M-Files Server. This affects an unknown part of the component Token Handler. Performing a manipulation results in log file. This vulnerability is known as CVE-2022-4858. Attacking locally is a requirement. No exploit is available. You should upgrade the affected component.
Details
A vulnerability, which was classified as problematic, was found in M-Files Server. This affects some unknown functionality of the component Token Handler. The manipulation with an unknown input leads to a log file vulnerability. CWE is classifying the issue as CWE-532. Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information. This is going to have an impact on confidentiality. The summary by CVE is:
Insertion of Sensitive Information into Log Files in M-Files Server before 22.10.11846.0 could allow to obtain sensitive tokens from logs, if specific configurations were set.
The weakness was published 12/30/2022. The advisory is shared at m-files.com. This vulnerability is uniquely identified as CVE-2022-4858 since 12/30/2022. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
Upgrading to version 22.10.11846.0 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
- 21.11.10775.0
- 21.12.10873.0
- 22.1.11017.1
- 22.2.11051.0
- 22.3.11164.0
- 22.3.11237.1
- 22.5.11356.0
- 22.6.11505.0
- 22.6.11534.1
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.7VulDB Meta Temp Score: 4.7
VulDB Base Score: 2.3
VulDB Temp Score: 2.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CNA Base Score: 4.4
CNA Vector (M-Files Corporation): 🔍
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: Log fileCWE: CWE-532 / CWE-200 / CWE-284
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Server 22.10.11846.0
Timeline
12/30/2022 🔍12/30/2022 🔍
12/30/2022 🔍
02/23/2026 🔍
Sources
Advisory: m-files.comStatus: Confirmed
CVE: CVE-2022-4858 (🔍)
GCVE (CVE): GCVE-0-2022-4858
GCVE (VulDB): GCVE-100-217065
Entry
Created: 12/30/2022 15:17Updated: 02/23/2026 12:23
Changes: 12/30/2022 15:17 (49), 01/26/2023 09:57 (11), 08/28/2024 15:04 (17), 02/23/2026 12:23 (1)
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.