DrayTek Vigor3900/Vigor2960/Vigor300B up to 1.5.1 /cgi-bin/activate.cgi ticket out-of-bounds write
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in DrayTek Vigor3900, Vigor2960 and Vigor300B up to 1.5.1. Affected by this issue is some unknown functionality of the file /cgi-bin/activate.cgi. Performing a manipulation of the argument ticket as part of HTTP Request results in out-of-bounds write. This vulnerability was named CVE-2020-10824. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability, which was classified as critical, was found in DrayTek Vigor3900, Vigor2960 and Vigor300B up to 1.5.1 (Router Operating System). This affects an unknown code of the file /cgi-bin/activate.cgi. The manipulation of the argument ticket as part of a HTTP Request leads to a out-of-bounds write vulnerability. CWE is classifying the issue as CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
A stack-based buffer overflow in /cgi-bin/activate.cgi through ticket parameter on Draytek Vigor3900, Vigor2960, and Vigor300B devices before 1.5.1 allows remote attackers to achieve code execution via a remote HTTP request (issue 2 of 3).
The weakness was presented 03/26/2020. This vulnerability is uniquely identified as CVE-2020-10824 since 03/22/2020. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
See VDB-152377, VDB-152376, VDB-152375 and VDB-152374 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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.5
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
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: Out-of-bounds writeCWE: CWE-787 / CWE-119
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
03/22/2020 🔍03/26/2020 🔍
03/27/2020 🔍
05/05/2025 🔍
Sources
Advisory: slashd.gaStatus: Not defined
Confirmation: 🔍
CVE: CVE-2020-10824 (🔍)
GCVE (CVE): GCVE-0-2020-10824
GCVE (VulDB): GCVE-100-152373
See also: 🔍
Entry
Created: 03/27/2020 07:41Updated: 05/05/2025 19:43
Changes: 03/27/2020 07:41 (38), 03/27/2020 07:46 (18), 10/05/2020 08:35 (1), 05/12/2024 07:18 (17), 05/05/2025 19:43 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.