CVE Intelligence
CISA KEV Critical exploit reference

CVE-2014-8361 — Realtek SDK Improper Input Validation Vulnerability

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.

Published May 1, 2015 · Updated Oct 13, 2026 · Sources: CISA Known Exploited Vulnerabilities, NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: mitre

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

How the score was calculated
  • Confirmed exploitation (CISA KEV)+35
  • Public exploit/PoC (metasploit, exploitdb)+20
  • EPSS 100% (30-day exploitation probability)+15
  • Technical severity (critical)+10
  • Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Confirmed
CISA KEV, listed Sep 18, 2023
EPSS FIRST
99.98%
ahead of 100% of scored CVEs · Oct 15, 2026
Affects
Aterm
W1200ex Firmware and 25 more
CVSS base
9.8
Critical · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Active
none · proof-of-concept · active
Automatable
Yes
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

CISA required action CISA

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

US federal deadline: Oct 9, 2023 — passed 1103 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Aterm W1200ex Firmware, Aterm W1200ex-ms Firmware, Aterm W300p Firmware…).
  2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
  3. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  4. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  5. EPSS ahead of 100% of scored CVEs: prioritize it in the patch queue.
  6. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Aterm W1200ex Firmware ≤ 1.3.1 Vulnerable NIST National Vulnerability Database
Aterm W1200ex-ms Firmware ≤ 1.3.1 Vulnerable NIST National Vulnerability Database
Aterm W300p Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Aterm W500p Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Aterm Wf300hp2 Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Aterm Wf800hp Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Aterm Wg1200hp Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Aterm Wg1200hp2 Firmware ≤ 2.5.0 Vulnerable NIST National Vulnerability Database
Aterm Wg1200hp3 Firmware ≤ 1.3.1 Vulnerable NIST National Vulnerability Database
Aterm Wg1200hs Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Aterm Wg1200hs2 Firmware ≤ 2.5.0 Vulnerable NIST National Vulnerability Database
Aterm Wg1800hp3 Firmware ≤ 1.5.1 Vulnerable NIST National Vulnerability Database
Aterm Wg1800hp4 Firmware ≤ 1.3.1 Vulnerable NIST National Vulnerability Database
Aterm Wg1900hp Firmware ≤ 2.5.1 Vulnerable NIST National Vulnerability Database
Aterm Wg1900hp2 Firmware ≤ 1.3.1 Vulnerable NIST National Vulnerability Database
Aterm Wr8165n Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Dlink Dir-501 Firmware ≤ 1.01b04 Vulnerable NIST National Vulnerability Database
Dlink Dir-515 Firmware ≤ 1.01b04 Vulnerable NIST National Vulnerability Database
Dlink Dir-600l Firmware ≤ 2.056b06≤ 1.15 Vulnerable NIST National Vulnerability Database
Dlink Dir-605l Firmware ≤ 1.14b06≤ 3.03b07≤ 2.07b02 Vulnerable NIST National Vulnerability Database
Dlink Dir-615 Firmware ≤ 6.06b03version 10.01b02 Vulnerable NIST National Vulnerability Database
Dlink Dir-619l Firmware ≤ 2.07b02≤ 1.15 Vulnerable NIST National Vulnerability Database
Dlink Dir-809 Firmware ≤ 1.04b02 Vulnerable NIST National Vulnerability Database
Dlink Dir-900l Firmware < 1.15b01 Vulnerable NIST National Vulnerability Database
Dlink Dir-905l Firmware ≤ 2.05b01 Vulnerable NIST National Vulnerability Database
Realtek Realtek Sdk versions not specified by the source Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
9.8 CVSS 3.1 Critical 3.9 5.9 nvd@nist.gov via NIST National Vulnerability Database
9.8 CVSS 3.1 Critical 3.9 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database
9.8 CVSS 3.1 Critical — — GitHub, Inc. via GitHub Security Advisories
9.8 CVSS 3.1 Critical — — CISA-ADP via CVE Program (cve.org) e CISA ADP
10.0 CVSS 2.0 High 10.0 10.0 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

Listed
Sep 18, 2023
Federal deadline
Oct 9, 2023
passed 1103 day(s) ago
Ransomware use
Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

Public exploits, PoCs and detection templates

Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.

Metasploit modules

Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.

EPSS over time FIRST

Oct 12, 2026 → Oct 15, 2026 · 4 reading(s) · max 99.98%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Hunt retroactively in logs from before Sep 18, 2023 (KEV listing): exploitation may have started earlier.
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Affected products added · dlink/dir-905l firmware, dlink/dir-605l firmware, dlink/dir-600l firmware, dlink/dir-619l firmware, dlink/dir-809 firmwa
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 9.8
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Added to CISA KEV (detected)
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Record created in this database
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • 2023
  • Added to CISA KEV catalog
    Sep 17, 2023 · CISA
  • 2015
  • CVE published
    May 1, 2015 · mitre

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 13, 2026 – Oct 13, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

15 on the record

Elsewhere on this site

Aterm
every CVE for this vendor
2023-09
what else CISA listed that month

Related CVEs (same products)

  • High CVE-2026-42374 D-Link DIR-600L B1 Hardcoded Telnet Backdoor Credentials May 4, 2026
  • High CVE-2026-42372 D-Link DIR-605L A1 Hardcoded Telnet Backdoor Credentials May 4, 2026
  • High CVE-2026-42373 D-Link DIR-605L B2 Hardcoded Telnet Backdoor Credentials May 4, 2026
  • High CVE-2026-42375 D-Link DIR-600L A1 Hardcoded Telnet Backdoor Credentials May 4, 2026
  • High CVE-2026-5983 D-Link DIR-605L POST Request formSetDDNS buffer overflow Apr 9, 2026
  • High CVE-2026-5984 D-Link DIR-605L POST Request formSetLog buffer overflow Apr 9, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No CWE classification.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2014-8361 is "Realtek SDK Improper Input Validation Vulnerability", rated Critical. It affects W1200ex Firmware (Aterm); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 9.8 describes technical severity. EPSS 99.98% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.