StrongDM sdm up to 47.49.0 Windows Service privileges management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in StrongDM sdm up to 47.49.0. It has been rated as critical. This affects an unknown function of the component Windows Service. This manipulation causes privileges management. This vulnerability is registered as CVE-2025-6182. The attack needs to be launched locally. No exploit is available.
Details
A vulnerability has been found in StrongDM sdm up to 47.49.0 and classified as critical. Affected by this vulnerability is an unknown function of the component Windows Service. The manipulation with an unknown input leads to a privileges management vulnerability. The CWE definition for the vulnerability is CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
The StrongDM Windows service incorrectly handled communication related to system certificate management. Attackers could exploit this behavior to install untrusted root certificates or remove trusted ones.
The advisory is shared at security.strongdm.com. This vulnerability is known as CVE-2025-6182 since 06/16/2025. The exploitation appears to be easy. An attack has to be approached locally. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/20/2025). MITRE ATT&CK project uses the attack technique T1068 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-25349). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
- 47.0
- 47.1
- 47.2
- 47.3
- 47.4
- 47.5
- 47.6
- 47.7
- 47.8
- 47.9
- 47.10
- 47.11
- 47.12
- 47.13
- 47.14
- 47.15
- 47.16
- 47.17
- 47.18
- 47.19
- 47.20
- 47.21
- 47.22
- 47.23
- 47.24
- 47.25
- 47.26
- 47.27
- 47.28
- 47.29
- 47.30
- 47.31
- 47.32
- 47.33
- 47.34
- 47.35
- 47.36
- 47.37
- 47.38
- 47.39
- 47.40
- 47.41
- 47.42
- 47.43
- 47.44
- 47.45
- 47.46
- 47.47
- 47.48
- 47.49.0
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 7.8VulDB Meta Temp Score: 7.8
VulDB Base Score: 7.8
VulDB Temp Score: 7.8
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: Privileges managementCWE: CWE-269 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
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
06/16/2025 CVE reserved08/20/2025 Advisory disclosed
08/20/2025 VulDB entry created
08/20/2025 VulDB entry last update
Sources
Advisory: security.strongdm.comStatus: Confirmed
CVE: CVE-2025-6182 (🔒)
GCVE (CVE): GCVE-0-2025-6182
GCVE (VulDB): GCVE-100-320845
EUVD: 🔒
Entry
Created: 08/20/2025 20:17Updated: 08/20/2025 21:01
Changes: 08/20/2025 20:17 (65), 08/20/2025 21:01 (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.