basicsecurity.net
Proof, not just disclosure.
Threats / D-Link / CVE-2020-29557
CVE-2020-29557 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

D-Link DIR-825 R1 Devices vulnerability

D-Link DIR-825 R1 devices contain a buffer overflow vulnerability in the web interface that may allow remote code execution.

Verdict

Today item — known-exploited.

A buffer overflow in the web interface of D-Link DIR-825 R1 devices enables unauthenticated remote code execution. The vulnerability is actively exploited in the wild with high exploit probability.

CISA KEV Yes · 2021-11-033EPSS 0.5432 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
37 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 2021-11-03).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.5432 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: D-Link, DIR-825 R1 Devices. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-119 Memory Buffer Bounds Error — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
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 HTTP request to the web interface that exceeds buffer boundaries.
Business
The device becomes a compromised network access point under attacker control.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I inject shellcode through the overflow to execute arbitrary commands on the device.
Business
Attackers gain persistent presence on the network perimeter with administrative privileges.
3

Lateral reach — past segmentation narrative 3

Attacker
I use the compromised router to intercept, modify, or redirect network traffic.
Business
Customer data and credentials transmitted across the network are exposed to interception and theft.
4

Data at risk — exfiltration narrative 4

Attacker
I establish the device as a pivot point to attack internal network resources.
Business
Internal systems and sensitive assets become accessible to lateral movement attacks.
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)
  • 37 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by mitre (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 mitreCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.