Security readout for executives and security teams
Plain-English summary
This CVE describes Draytek AP903, AP912C, and AP918R firmware using a hardcoded weak password for the routing daemon configuration. If reachable by an attacker on the network, the routing service could be controlled without authorization, creating risk of route manipulation, traffic interception, or outages.
Executive priority
Treat this as a high-priority network infrastructure issue where affected Draytek devices route or influence production traffic. The business concern is unauthorized route manipulation, traffic interception, or availability impact, not endpoint compromise. Prioritize inventory, isolation, and vendor remediation confirmation.
Technical view
The issue is an insecure configuration in ripd.conf where the password property uses a hardcoded weak password. Sources map this to CWE-276 and CWE-798 with CVSS 3.1 score 8.6, network attack vector, no privileges, and no user interaction. Listed versions are AP903 v1.4.18, AP912C v1.4.9, and AP918R v1.4.9.
Likely exposure
Organizations using the listed Draytek access point firmware versions are most likely exposed, especially where routing or management services are reachable from untrusted networks. The bundle’s structured affected-product fields are incomplete, so confirm against asset inventory and vendor records.
Exploitation context
The source bundle does not report CISA KEV listing or active exploitation. The described attack requires network access to the affected routing daemon and could allow unauthorized route control. No exploit maturity, internet-scale exploitation, or vendor advisory detail is supplied.
Researcher notes
Evidence is centered on the CVE description and one public reference. Affected product metadata is incomplete in the structured record, but the narrative names specific models and versions. Avoid assuming additional Draytek products, fixed versions, or exploitation without vendor or KEV confirmation.
Mitigation direction
- Check Draytek guidance for fixed firmware or configuration remediation.
- Restrict access to routing and management services to trusted administration networks.
- Remove affected devices from untrusted VLANs or internet-reachable segments.
- Monitor for unexpected route changes or routing daemon configuration changes.
- Prioritize replacement or isolation if no vendor fix is available.
Validation and detection
- Inventory Draytek AP903, AP912C, and AP918R devices and firmware versions.
- Confirm whether AP903 v1.4.18, AP912C v1.4.9, or AP918R v1.4.9 are deployed.
- Review network reachability to routing and management services.
- Check device configuration for the referenced ripd.conf password behavior.
- Correlate route changes with approved maintenance activity.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-276: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-798: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-44643 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H3.94.7CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
8.6HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.notion.so/Misconfiguration-in-Draytek-AP903-23a54a1113e780aca7f2d21dbdab9db8CVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Default Permissions
Incorrect Default Permissions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Use of Hard-coded Credentials
Use of Hard-coded Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.