cve.bz

CVE-2014-8361 Realtek SDK Improper Input Validation Vulnerability

9.8 criticalKEVExploitEPSS >99.9%

Critical (9.8) in Realtek SDK. In CISA KEV since 2023-09-18. EPSS >99.9% estimated probability of exploitation activity in the next 30 days.

On this page
The miniigd SOAP service in Realtek SDK allows remote attackers to execute arbitrary code via a crafted NewInternalClient request, as exploited in the wild through 2023.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
>99.9% (unchanged from >99.9% a week ago; >99.9% 30 days ago) estimated probability of exploitation activity in the next 30 days; 100th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2023-09-18, due 2023-10-09
CISA's assessment (SSVC)
Exploitation: active · Automatable: yes · Technical impact: total, assessed 2025-02-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2014-8361 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2014-8361?via=ask-ai-copy and https://cve.bz/cve/CVE-2014-8361?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2014-8361 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
dlink:dir-905l_firmwarethrough 2.05b01
dlink:dir-605l_firmwarethrough 1.14b06
dlink:dir-600l_firmwarethrough 1.15
dlink:dir-619l_firmwarethrough 1.15
dlink:dir-619l_firmwarethrough 2.07b02
dlink:dir-605l_firmwarethrough 2.07b02
dlink:dir-605l_firmwarethrough 3.03b07
dlink:dir-600l_firmwarethrough 2.056b06
dlink:dir-809_firmwarethrough 1.04b02
dlink:dir-900l_firmwarebefore 1.15b01
dlink:dir-501_firmwarethrough 1.01b04
dlink:dir-515_firmwarethrough 1.01b04
dlink:dir-615_firmware10.01b02
dlink:dir-615_firmwarethrough 6.06b03
aterm:wg1900hp2_firmwarethrough 1.3.1
aterm:wg1900hp_firmwarethrough 2.5.1
aterm:wg1800hp4_firmwarethrough 1.3.1
aterm:wg1800hp3_firmwarethrough 1.5.1
aterm:wg1200hs2_firmwarethrough 2.5.0
aterm:wg1200hp3_firmwarethrough 1.3.1
aterm:wg1200hp2_firmwarethrough 2.5.0
aterm:w1200ex_firmwarethrough 1.3.1
aterm:w1200ex-ms_firmwarethrough 1.3.1

Public exploits

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

  • Emerging Threats Open ET EXPLOIT Realtek SDK Miniigd UPnP SOAP Command Execution CVE-2014-8361 - Outbound sid 2027339
  • Emerging Threats Open ET EXPLOIT Realtek SDK Miniigd UPnP SOAP Command Execution CVE-2014-8361 sid 2025132

References

Check your stackJSON