StrongDM sdm-cli up to 47.38.0 Windows Service os command injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.8 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in StrongDM sdm-cli up to 47.38.0. The affected element is an unknown function of the component Windows Service. Performing a manipulation results in os command injection. This vulnerability is known as CVE-2025-6181. Attacking locally is a requirement. No exploit is available.
Details
A vulnerability was found in StrongDM sdm-cli up to 47.38.0. It has been classified as critical. This affects some unknown processing of the component Windows Service. The manipulation with an unknown input leads to a os command injection vulnerability. CWE is classifying the issue as CWE-78. The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
The StrongDM Windows service incorrectly handled input validation. Authenticated attackers could potentially exploit this leading to privilege escalation.
The advisory is shared at security.strongdm.com. This vulnerability is uniquely identified as CVE-2025-6181 since 06/16/2025. The exploitability is told 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 T1202 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-25351). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
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.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: Os command injectionCWE: CWE-78 / CWE-77 / CWE-74
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-6181 (🔒)
GCVE (CVE): GCVE-0-2025-6181
GCVE (VulDB): GCVE-100-320865
EUVD: 🔒
Entry
Created: 08/20/2025 20:22Updated: 08/20/2025 21:01
Changes: 08/20/2025 20:22 (65), 08/20/2025 21:01 (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.