DrayTek Vigor3900/Vigor2960/Vigor300B up to 1.5.0 Debug Mode /cgi-bin/activate.cgi HTTP Request os command injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in DrayTek Vigor3900, Vigor2960 and Vigor300B up to 1.5.0. This vulnerability affects unknown code of the file /cgi-bin/activate.cgi of the component Debug Mode. The manipulation as part of HTTP Request leads to os command injection. This vulnerability is referenced as CVE-2020-10826. Remote exploitation of the attack is possible. No exploit is available. It is recommended to upgrade the affected component.
Details
A vulnerability was found in DrayTek Vigor3900, Vigor2960 and Vigor300B up to 1.5.0 (Router Operating System) and classified as critical. This issue affects some unknown processing of the file /cgi-bin/activate.cgi of the component Debug Mode. The manipulation as part of a HTTP Request leads to a os command injection vulnerability. Using CWE to declare the problem leads to CWE-78. The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
/cgi-bin/activate.cgi on Draytek Vigor3900, Vigor2960, and Vigor300B devices before 1.5.1 allows remote attackers to achieve command injection via a remote HTTP request in DEBUG mode.
The weakness was published 03/26/2020. The identification of this vulnerability is CVE-2020-10826 since 03/22/2020. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1202 according to MITRE ATT&CK.
Upgrading to version 1.5.1 eliminates this vulnerability.
Similar entries are available at VDB-152377, VDB-152376, VDB-152374 and VDB-152373. Be aware that VulDB is the high quality source for vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Os command injectionCWE: CWE-78 / CWE-77 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Vigor3900/Vigor2960/Vigor300B 1.5.1
Timeline
03/22/2020 🔍03/26/2020 🔍
03/27/2020 🔍
05/05/2025 🔍
Sources
Advisory: slashd.gaStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2020-10826 (🔍)
GCVE (CVE): GCVE-0-2020-10826
GCVE (VulDB): GCVE-100-152375
See also: 🔍
Entry
Created: 03/27/2020 07:43Updated: 05/05/2025 19:43
Changes: 03/27/2020 07:43 (40), 03/27/2020 07:48 (18), 10/05/2020 08:38 (1), 05/12/2024 07:29 (18), 05/05/2025 19:43 (4)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.