CVE-2024-41335

Feb. 28, 2025, 10:15 p.m.

7.5
High

Description

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.

Product(s) Impacted

Product Versions
Draytek Vigor 165/166
  • ['before v4.2.6']
Draytek Vigor 2620/LTE200
  • ['before v3.9.8.8']
Draytek Vigor 2860/2925
  • ['before v3.9.7']
Draytek Vigor 2862/2926
  • ['before v3.9.9.4']
Draytek Vigor 2133/2762/2832
  • ['before v3.9.8']
Draytek Vigor 2135/2765/2766
  • ['before v4.4.5.1']
Draytek Vigor 2865/2866/2927
  • ['before v4.4.5.3']
Draytek Vigor 2962/3910
  • ['before v4.3.2.7']
Draytek Vigor 3912
  • ['before v4.3.5.2']
Draytek Vigor 2925
  • ['up to v3.9.6']

Weaknesses

Common security weaknesses mapped to this vulnerability.

CWE-203
Observable Discrepancy
The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor, which exposes security-relevant information about the state of the product, such as whether a particular operation was successful or not.

CVSS Score

7.5 / 10

CVSS Data - 3.1

  • Attack Vector: NETWORK
  • Attack Complexity: LOW
  • Privileges Required: NONE
  • Scope: UNCHANGED
  • Confidentiality Impact: HIGH
  • Integrity Impact: NONE
  • Availability Impact: NONE
  • CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

    View Vector String

Timeline

Published: Feb. 27, 2025, 9:15 p.m.
Last Modified: Feb. 28, 2025, 10:15 p.m.

Status : Awaiting Analysis

CVE has been recently published to the CVE List and has been received by the NVD.

More info

Source

cve@mitre.org

*Disclaimer: Some vulnerabilities do not have an associated CPE. To enhance the data, we use AI to infer CPEs based on CVE details. This is an automated process and might not always be accurate.