Devolutions Remote Desktop Manager up to 2024.3.29/2025.1.25 on Windows Variable ELEVATED_PASSWORD improper authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Devolutions Remote Desktop Manager up to 2024.3.29/2025.1.25 on Windows. Affected by this issue is some unknown functionality of the component Variable Component. The manipulation of the argument ELEVATED_PASSWORD leads to improper authorization. This vulnerability is referenced as CVE-2025-2600. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability was found in Devolutions Remote Desktop Manager up to 2024.3.29/2025.1.25 on Windows. It has been rated as critical. This issue affects an unknown code of the component Variable Component. The manipulation of the argument ELEVATED_PASSWORD with an unknown input leads to a improper authorization vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Improper authorization in the variable component in Devolutions Remote Desktop Manager on Windows allows an authenticated password to use the ELEVATED_PASSWORD variable even though not allowed by the "Allow password in variable policy". This issue affects Remote Desktop Manager versions from 2025.1.24 through 2025.1.25, and all versions up to 2024.3.29.
The advisory is shared at devolutions.net. The identification of this vulnerability is CVE-2025-2600 since 03/21/2025. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/02/2025). MITRE ATT&CK project uses the attack technique T1548.002 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
- 2024.3.0
- 2024.3.1
- 2024.3.2
- 2024.3.3
- 2024.3.4
- 2024.3.5
- 2024.3.6
- 2024.3.7
- 2024.3.8
- 2024.3.9
- 2024.3.10
- 2024.3.11
- 2024.3.12
- 2024.3.13
- 2024.3.14
- 2024.3.15
- 2024.3.16
- 2024.3.17
- 2024.3.18
- 2024.3.19
- 2024.3.20
- 2024.3.21
- 2024.3.22
- 2024.3.23
- 2024.3.24
- 2024.3.25
- 2024.3.26
- 2024.3.27
- 2024.3.28
- 2024.3.29
- 2025.1.0
- 2025.1.1
- 2025.1.2
- 2025.1.3
- 2025.1.4
- 2025.1.5
- 2025.1.6
- 2025.1.7
- 2025.1.8
- 2025.1.9
- 2025.1.10
- 2025.1.11
- 2025.1.12
- 2025.1.13
- 2025.1.14
- 2025.1.15
- 2025.1.16
- 2025.1.17
- 2025.1.18
- 2025.1.19
- 2025.1.20
- 2025.1.21
- 2025.1.22
- 2025.1.23
- 2025.1.24
- 2025.1.25
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: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: 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
03/21/2025 🔍03/26/2025 🔍
03/26/2025 🔍
07/02/2025 🔍
Sources
Advisory: DEVO-2025-0005Status: Confirmed
CVE: CVE-2025-2600 (🔍)
GCVE (CVE): GCVE-0-2025-2600
GCVE (VulDB): GCVE-100-301445
Entry
Created: 03/26/2025 19:56Updated: 07/02/2025 20:07
Changes: 03/26/2025 19:56 (56), 07/02/2025 20:07 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.