CVE-2025-44643: High severity DrayTek AP903 vulnerability

Published Aug 4, 2025
·
Updated

Certain Draytek products are affected by Insecure Configuration. This affects AP903 v1.4.18 and AP912C v1.4.9 and AP918R v1.4.9. The setting of the password property in the ripd.conf configuration file sets a hardcoded weak password, posing a security risk. An attacker with network access could exploit this to gain unauthorized control over the routing daemon, potentially altering network routes or intercepting traffic.

Affected Software

3 affected components
DrayTek AP903
DrayTek AP912C
DrayTek AP918R

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    For affected Draytek products, update the 'password' setting in ripd.conf to a strong, non-weak password to avoid the hardcoded weak password risk (AP903 v1.4.18, AP912C v1.4.9, AP918R v1.4.9).

    ripd.conf password property = Use a strong password instead of the hardcoded weak password

Event History

Aug 4, 2025
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Data Sourced
via NVD·03:15 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-44643?

CVE-2025-44643 is classified as a high severity vulnerability due to the presence of a hardcoded weak password affecting sensitive configurations.

2

How do I fix CVE-2025-44643?

To fix CVE-2025-44643, update your Draytek products to the latest firmware version that addresses the insecure permissions issue.

3

Which Draytek products are affected by CVE-2025-44643?

CVE-2025-44643 affects the Draytek AP903, AP912C, and AP918R models specifically in certain firmware versions.

4

What risk does CVE-2025-44643 pose to users?

CVE-2025-44643 poses a risk of unauthorized access and potential takeover of network configurations due to the insecure permissions.

5

Is there a workaround for CVE-2025-44643 if I cannot update immediately?

A temporary workaround for CVE-2025-44643 is to manually secure the configuration files and change any default passwords as an interim measure.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203