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

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

• draytek vigor165 firmwarebefore 4.2.6
• draytek vigor166 firmwarebefore 4.2.6
• draytek vigor2133 firmwarebefore 3.9.8
• draytek vigor2135 firmwarebefore 4.4.5.1
• draytek vigor2620 firmwarebefore 3.9.8.8
• draytek vigor2762 firmwarebefore 3.9.8
• draytek vigor2765 firmwarebefore 4.4.5.1
• draytek vigor2766 firmwarebefore 4.4.5.1
• draytek vigor2832 firmwarebefore 3.9.8
• draytek vigor2860 firmwarebefore 3.9.7
• draytek vigor2862 firmwarebefore 3.9.9.4
• draytek vigor2865 firmwarebefore 4.4.5.3
• draytek vigor2866 firmwarebefore 4.4.5.3
• draytek vigor2925 firmwarebefore 3.9.7
• draytek vigor2926 firmwarebefore 3.9.9.4
• draytek vigor2927 firmwarebefore 4.4.5.3
• draytek vigor2962 firmwarebefore 4.3.2.7
• draytek vigor3910 firmwarebefore 4.3.2.7
• draytek vigor3912 firmwarebefore 4.3.5.2
• draytek vigorlte200 firmwarebefore 3.9.8.8

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Root cause

A certificate validation error is silently swallowed instead of terminating the connection. Often, code added for a test environment makes its way into production.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

1override fun checkServerTrusted(chain: Array<X509Certificate>, type: String) {2  // Left empty for the test environment3}

1val client = OkHttpClient.Builder()2  .certificatePinner(3    CertificatePinner.Builder()4      .add("api.sirius.example", "sha256/…")5      .build()6  ).build()

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.