basicsecurity.net
Proof, not just disclosure.
Threats / DrayTek / CVE-2021-20124
CVE-2021-20124 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

DrayTek VigorConnect vulnerability

DrayTek VigorConnect contains a path traversal vulnerability in file download functionality that allows unauthenticated attackers to download arbitrary files with root privileges.

Verdict

Today item — known-exploited.

An unauthenticated remote attacker can exploit path traversal in the WebServlet endpoint to access sensitive files on the system. The vulnerability is actively exploited in the wild and carries high severity due to lack of authentication requirements and root-level file access.

CISA KEV Yes · 2024-09-033EPSS 0.69248 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
233 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-09-03).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.69248 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: DrayTek, VigorConnect. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-22 Path Traversal — weakness family: Path traversal / file.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-22 · Path TraversalPath traversal / file
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a malicious file path using traversal sequences to bypass directory restrictions in the download endpoint.
Business
Sensitive system files become accessible to external threat actors without credentials.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I retrieve configuration files, private keys, or other root-owned data from the compromised appliance.
Business
Confidential credentials and system secrets are exposed, enabling lateral movement and further compromise.
3

Lateral reach — past segmentation narrative 3

Attacker
I use extracted credentials or system information to establish persistent access or pivot to connected infrastructure.
Business
The organization's network perimeter is breached, with potential for widespread system compromise and data exfiltration.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 233 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by tenable (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by tenableCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.