LiveActive security incident?Get immediate response
CVE Record

CVE-2020-10824: A stack-based buffer overflow in /cgi-bin/activate.cgi through ticket parameter on Draytek Vigor3900, Vigor...

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).

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2020-10824 is a critical flaw in specific DrayTek Vigor devices. A remote attacker could trigger a stack buffer overflow through an HTTP request and potentially run code on the device. Because these devices may sit on network edges, exposed vulnerable systems should be treated as urgent.

Executive priority

Prioritize remediation immediately for any internet-reachable affected device. The flaw is unauthenticated, network-accessible, and rated critical, creating potential for full device compromise. Devices not externally reachable still need scheduled remediation and access restriction.

Technical view

The issue is a stack-based buffer overflow in /cgi-bin/activate.cgi via the ticket parameter on DrayTek Vigor3900, Vigor2960, and Vigor300B firmware before 1.5.1. The CVSS 3.1 score is 9.8, with network attack vector, no authentication, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely where Vigor3900, Vigor2960, or Vigor300B devices run firmware earlier than 1.5.1 and accept HTTP access from untrusted networks. The provided CVE data does not list CPEs, so asset confirmation is required.

Exploitation context

The CVE states remote code execution is possible via a remote HTTP request. CISA KEV status is false in the provided bundle, and no cited source here confirms active exploitation. Public vulnerability details exist, so internet-facing devices remain high risk.

Researcher notes

Evidence supports affected models and the pre-1.5.1 version boundary, but the structured affected-product data in the bundle is incomplete. Do not assume additional DrayTek models are affected from this bundle alone. Active exploitation is not established by the provided sources.

Mitigation direction

  • Upgrade affected DrayTek devices to firmware 1.5.1 or later.
  • Review DrayTek’s advisory for product-specific firmware guidance.
  • Restrict HTTP management access to trusted administrative networks.
  • Remove internet exposure for affected device web interfaces where possible.
  • Monitor vendor guidance for any additional remediation notes.

Validation and detection

  • Inventory Vigor3900, Vigor2960, and Vigor300B devices.
  • Confirm each device firmware version is 1.5.1 or later.
  • Check whether device HTTP interfaces are reachable from untrusted networks.
  • Review access logs for unexpected requests to /cgi-bin/activate.cgi.
  • Document exceptions where devices cannot be upgraded immediately.
Prepared
Confidence
high
Sources
4

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 · low confidence lookup

CWE-787: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-10824 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2020-10824Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.