Grandstream UCM6510 up to 1.0.20.52 excessive authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.1 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Grandstream UCM6510 up to 1.0.20.52. This vulnerability affects unknown code. The manipulation leads to excessive authentication. This vulnerability is referenced as CVE-2025-28172. No exploit is available.
Details
A vulnerability, which was classified as problematic, has been found in Grandstream UCM6510 up to 1.0.20.52. This issue affects an unknown code. The manipulation with an unknown input leads to a excessive authentication vulnerability. Using CWE to declare the problem leads to CWE-307. The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame, making it more susceptible to brute force attacks. Impacted is confidentiality. The summary by CVE is:
Grandstream Networks UCM6510 v1.0.20.52 and before is vulnerable to Improper Restriction of Excessive Authentication Attempts. An attacker can perform an arbitrary number of authentication attempts using different passwords and eventually gain access to the targeted account using a brute force attack.
The identification of this vulnerability is CVE-2025-28172 since 03/11/2025. The exploitation is known to be difficult. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1110.001 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
- 1.0.20.0
- 1.0.20.1
- 1.0.20.2
- 1.0.20.3
- 1.0.20.4
- 1.0.20.5
- 1.0.20.6
- 1.0.20.7
- 1.0.20.8
- 1.0.20.9
- 1.0.20.10
- 1.0.20.11
- 1.0.20.12
- 1.0.20.13
- 1.0.20.14
- 1.0.20.15
- 1.0.20.16
- 1.0.20.17
- 1.0.20.18
- 1.0.20.19
- 1.0.20.20
- 1.0.20.21
- 1.0.20.22
- 1.0.20.23
- 1.0.20.24
- 1.0.20.25
- 1.0.20.26
- 1.0.20.27
- 1.0.20.28
- 1.0.20.29
- 1.0.20.30
- 1.0.20.31
- 1.0.20.32
- 1.0.20.33
- 1.0.20.34
- 1.0.20.35
- 1.0.20.36
- 1.0.20.37
- 1.0.20.38
- 1.0.20.39
- 1.0.20.40
- 1.0.20.41
- 1.0.20.42
- 1.0.20.43
- 1.0.20.44
- 1.0.20.45
- 1.0.20.46
- 1.0.20.47
- 1.0.20.48
- 1.0.20.49
- 1.0.20.50
- 1.0.20.51
- 1.0.20.52
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.1VulDB Meta Temp Score: 3.1
VulDB Base Score: 3.1
VulDB Temp Score: 3.1
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: Excessive authenticationCWE: CWE-307 / CWE-799 / CWE-400
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
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/11/2025 CVE reserved07/29/2025 Advisory disclosed
07/29/2025 VulDB entry created
08/01/2025 VulDB entry last update
Sources
Status: Not definedCVE: CVE-2025-28172 (🔒)
GCVE (CVE): GCVE-0-2025-28172
GCVE (VulDB): GCVE-100-318035
Entry
Created: 07/29/2025 17:56Updated: 08/01/2025 06:22
Changes: 07/29/2025 17:56 (51), 08/01/2025 06:22 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.