Threats / D-Link / CVE-2022-37055
CVE-2022-37055
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
D-Link Routers vulnerability
D-Link routers contain a buffer overflow vulnerability (CWE-120) affecting confidentiality, integrity, and availability. The vulnerability is actively exploited in the wild. Affected products may be end-of-life or end-of-service.
Verdict
Today item — known-exploited.
A buffer overflow in D-Link routers enables remote code execution with high impact across confidentiality, integrity, and availability. Active exploitation in the wild and end-of-life status create urgent risk for unpatched deployments.
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
5 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 2025-12-08).
Probability (EPSS)
EPSS 0.57037 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: D-Link, Routers. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-120 Buffer Copy without Size Check — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution 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 board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious input that overflows a buffer in the router firmware to inject and execute arbitrary code.
Business
Attackers gain complete control of network perimeter devices, enabling lateral movement, data exfiltration, and persistent compromise of internal systems.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I leverage code execution to modify router configuration, intercept traffic, or establish a botnet node.
Business
Network traffic is exposed to eavesdropping, man-in-the-middle attacks, and the organization becomes part of a distributed attack infrastructure.
3
Lateral reach — past segmentation narrative 3
Attacker
I maintain persistence by installing firmware-level backdoors that survive reboots.
Business
Long-term compromise remains undetected; remediation requires forensic investigation and complete device replacement or secure reimaging.
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