CVE-2022-4861: Incorrect Implementation of Authentication Algorithm
First published: Fri Dec 30 2022(Updated: )
Incorrect implementation in authentication protocol in M-Files Client before 22.5.11356.0 allows high privileged user to get other users tokens to another resource.
Credit: security@m-files.com security@m-files.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| M-files M-files Client | <22.5.11356.0 | |
| <22.5.11356.0 |
Remedy
Upgrade to non-vulnerable version.
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is CVE-2022-4861?
CVE-2022-4861 is a vulnerability in the authentication protocol implementation in M-Files Client before version 22.5.11356.0.
What is the severity of CVE-2022-4861?
The severity of CVE-2022-4861 is medium with a severity value of 4.9.
How does CVE-2022-4861 affect M-Files Client?
CVE-2022-4861 allows a high privileged user to get other users' tokens to another resource in M-Files Client before version 22.5.11356.0.
How can I fix CVE-2022-4861?
To fix CVE-2022-4861, update your M-Files Client to version 22.5.11356.0 or later.
- collector/nvd-index
- agent/weakness
- agent/type
- agent/softwarecombine
- agent/remedy
- agent/severity
- agent/title
- agent/description
- agent/first-publish-date
- agent/event
- agent/references
- agent/author
- agent/tags
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- collector/nvd-api
- source/NVD
- vendor/m-files
- canonical/m-files m-files client