LiveActive security incident?Get immediate response
CVE Record

CVE-2020-10825: A stack-based buffer overflow in /cgi-bin/activate.cgi while base64 decoding ticket parameter on Draytek Vi...

A stack-based buffer overflow in /cgi-bin/activate.cgi while base64 decoding 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 3 of 3).

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This vulnerability affects DrayTek Vigor3900, Vigor2960, and Vigor300B devices running firmware before 1.5.1. A remote attacker could trigger memory corruption through an HTTP request and potentially run code on the device. Because these devices often sit at network boundaries, compromise could create serious business risk.

Executive priority

Treat as urgent for any affected DrayTek boundary devices. The issue is remotely reachable, unauthenticated, and rated critical, but the provided sources do not prove active exploitation.

Technical view

CVE-2020-10825 is a stack-based buffer overflow in /cgi-bin/activate.cgi during base64 decoding of the ticket parameter. The CVSS 3.1 score is 9.8, with network attack vector, low complexity, no privileges, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely where affected DrayTek Vigor3900, Vigor2960, or Vigor300B devices run firmware before 1.5.1, especially if their HTTP management surface is reachable from untrusted networks.

Exploitation context

The provided bundle supports remote code execution via a remote HTTP request. It does not show CISA KEV listing or other evidence of active exploitation, so active exploitation should not be assumed from these sources alone.

Researcher notes

The affected CPE data in the bundle is incomplete, but the CVE description names Vigor3900, Vigor2960, and Vigor300B before 1.5.1. Focus validation on firmware identification, management-plane exposure, and vendor advisory alignment.

Mitigation direction

  • Identify Vigor3900, Vigor2960, and Vigor300B devices in the environment.
  • Upgrade affected devices running firmware before 1.5.1 per DrayTek guidance.
  • Check DrayTek advisory for any model-specific firmware or support notes.
  • Limit untrusted access to device HTTP management surfaces where operationally feasible.
  • Monitor vendor guidance for any later remediation instructions.

Validation and detection

  • Confirm each device model and firmware version through approved administrative channels.
  • Flag Vigor3900, Vigor2960, and Vigor300B firmware before 1.5.1 as vulnerable.
  • Review logs for unexpected requests to /cgi-bin/activate.cgi without using exploit payloads.
  • Verify internet-facing exposure of device HTTP interfaces through asset management data.
  • Document upgraded devices and any remaining exceptions.
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-10825 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-10825Attack 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.