DrayTek AP903/AP912C/AP918R Setting clients.conf secret weak password
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.7 | $0-$5k | 0.00 |
Summary
A vulnerability was found in DrayTek AP903, AP912C and AP918R. It has been rated as problematic. This affects an unknown function of the file clients.conf of the component Setting Handler. The manipulation of the argument secret leads to weak password. This vulnerability is traded as CVE-2025-44643. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in DrayTek AP903, AP912C and AP918R (version unknown). It has been rated as problematic. This issue affects an unknown function of the file clients.conf of the component Setting Handler. The manipulation of the argument secret with an unknown input leads to a weak password vulnerability. Using CWE to declare the problem leads to CWE-521. The product does not require that users should have strong passwords, which makes it easier for attackers to compromise user accounts. Impacted is confidentiality. The summary by CVE is:
Certain Draytek products are affected by Insecure Permissions. This affects AP903 v1.4.18 and AP912C v1.4.9 and AP918R v1.4.9. The setting of the secret field in the FreeRadius-related clients.conf configuration file sets a hardcoded weak password, posing a security risk.
The identification of this vulnerability is CVE-2025-44643 since 04/22/2025. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1552 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.7VulDB Meta Temp Score: 3.7
VulDB Base Score: 3.7
VulDB Temp Score: 3.7
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: Weak passwordCWE: CWE-521
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
04/22/2025 CVE reserved08/04/2025 Advisory disclosed
08/04/2025 VulDB entry created
08/06/2025 VulDB entry last update
Sources
Status: Not definedCVE: CVE-2025-44643 (🔒)
GCVE (CVE): GCVE-0-2025-44643
GCVE (VulDB): GCVE-100-318689
Entry
Created: 08/04/2025 17:31Updated: 08/06/2025 04:24
Changes: 08/04/2025 17:31 (53), 08/06/2025 04:24 (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.