CVE-2024-41335: Draytek devices Vigor 165/166 prior to v4.2.6 , Vigor 2620/LTE200 prior to v3.9.8.8, Vigor 2860/2925 prior...
Draytek devices Vigor 165/166 prior to v4.2.6 , Vigor 2620/LTE200 prior to v3.9.8.8, Vigor 2860/2925 prior to v3.9.7, Vigor 2862/2926 prior to v3.9.9.4, Vigor 2133/2762/2832 prior to v3.9.8, Vigor 2135/2765/2766 prior to v4.4.5.1, Vigor 2865/2866/2927 prior to v4.4.5.3, Vigor 2962/3910 prior to v4.3.2.7, Vigor 3912 prior to v4.3.5.2, and Vigor 2925 up to v3.9.6 were discovered to utilize insecure versions of the functions strcmp and memcmp, allowing attackers to possibly obtain sensitive information via timing attacks.
Security readout for executives and security teams
Plain-English summary
This flaw affects multiple DrayTek Vigor router models running older firmware. The devices used comparison functions in a way that may leak sensitive information through timing differences. It is remotely reachable according to the CVSS vector and requires no authentication or user interaction, so exposed edge devices should be reviewed promptly.
Executive priority
Treat this as a high-priority edge-device confidentiality risk. It does not have confirmed active exploitation in the provided sources, but remote unauthenticated exposure on routers raises business urgency.
Technical view
CVE-2024-41335 is a CWE-203 observable discrepancy issue in DrayTek Vigor firmware. Insecure use of strcmp and memcmp may allow attackers to infer sensitive information through timing attacks. The CVSS 3.1 score is 7.5, driven by network access, low complexity, no privileges, and high confidentiality impact.
Likely exposure
Organizations using listed DrayTek Vigor models below the fixed firmware versions are potentially exposed, especially where the affected device is reachable over a network. The source data does not identify a specific vulnerable endpoint or configuration requirement.
Exploitation context
The CVE record describes possible sensitive information disclosure via timing attacks. It is not listed as KEV in the provided bundle, and no cited source in the bundle confirms active exploitation.
Researcher notes
The public data names affected model families and fixed firmware thresholds, but does not provide endpoint-level detail, proof-of-concept status, or exact secrets at risk. Avoid assuming broader product impact beyond the listed DrayTek Vigor devices.
Mitigation direction
Upgrade affected DrayTek Vigor devices to the fixed firmware version or later.
Prioritize internet-facing or remotely managed routers first.
Check DrayTek guidance for any model-specific mitigation or replacement advice.
Track the Faraday advisory and CVE record for updates.
Document devices that cannot be upgraded and assign compensating controls.
Validation and detection
Inventory DrayTek Vigor models and firmware versions across the environment.
Compare versions against each fixed release listed in the CVE description.
Identify whether affected routers are reachable from untrusted networks.
Review logs and monitoring for unusual access to exposed router services.
Confirm remediation by recording post-upgrade firmware versions.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · medium confidence lookup
CWE-203: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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.
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.
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-203 · source CWE mapping
Observable Discrepancy
Observable Discrepancy represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.