LiveActive security incident?Get immediate response
CVE Record

CVE-2020-10828: A stack-based buffer overflow in cvmd on Draytek Vigor3900, Vigor2960, and Vigor300B devices before 1.5.1 a...

A stack-based buffer overflow in cvmd on Draytek Vigor3900, Vigor2960, and Vigor300B devices before 1.5.1 allows remote attackers to achieve code execution via a remote HTTP request.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2020-10828 is a critical flaw in specific DrayTek Vigor devices. A remote attacker could potentially take control by sending a crafted HTTP request. For organizations still running affected firmware, this is an edge-device compromise risk with possible full confidentiality, integrity, and availability impact.

Executive priority

Treat as urgent for any affected device that is internet-facing or reachable by untrusted users. The business risk is full device compromise at the network edge, but priority depends on whether these older DrayTek models remain deployed.

Technical view

The CVE describes a stack-based buffer overflow in cvmd on DrayTek Vigor3900, Vigor2960, and Vigor300B devices before firmware 1.5.1. CVSS 3.1 rates it 9.8 with network access, low complexity, no privileges, no user interaction, and high CIA impact.

Likely exposure

Exposure is most likely where affected DrayTek Vigor3900, Vigor2960, or Vigor300B devices run firmware earlier than 1.5.1, especially if HTTP management or related services are reachable from untrusted networks.

Exploitation context

The supplied CVE record says remote code execution is possible via a remote HTTP request. The bundle does not show CISA KEV listing or other cited evidence of active exploitation, so active exploitation should not be asserted from these sources alone.

Researcher notes

Evidence supports unauthenticated network-reachable RCE characteristics from CVSS and the CVE description. The source bundle does not provide exploit details, affected CPEs, or proof of active exploitation. Validation should focus on model, firmware, and management-plane exposure.

Mitigation direction

  • Identify Vigor3900, Vigor2960, and Vigor300B devices in the environment.
  • Upgrade affected devices to DrayTek firmware 1.5.1 or later, following vendor guidance.
  • Restrict HTTP management exposure to trusted administrative networks.
  • Disable unnecessary remote access paths where operationally possible.
  • Monitor vendor advisory pages for model-specific remediation notes.

Validation and detection

  • Confirm each affected model’s firmware version is 1.5.1 or later.
  • Review perimeter exposure for reachable HTTP management interfaces.
  • Check asset inventory for unmanaged DrayTek devices.
  • Review device and network logs for unusual HTTP management traffic.
  • Verify compensating access controls after firmware remediation.
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-10828 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-10828Attack 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.