Security Resilience

CVE-2023-31814

Dlink Dir-300 Firmware ≤ 1.06

Published
23 May 2023
Modified
17 January 2025
Patch / advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0089 58th percentile
Risk Priority 73 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-31814 is a critical-severity Use of Incorrectly-Resolved Name or Reference (CWE-706) vulnerability in Dlink Dir-300 Firmware. Its CVSS base score is 9.8 (Critical).

Operationally, ranked in the top 42% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

D-Link DIR-300 firmware <=REVA1.06 and <=REVB2.06 is vulnerable to File inclusion via /model/__lang_msg.php.

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-41616Same product: Dlink Dir-300
CVE-2011-4723Same product: Dlink Dir-300
CVE-2024-0717Same product: Dlink Dir-300
CVE-2023-33782Same vendor: Dlink
CVE-2023-39666Same vendor: Dlink
CVE-2023-45579Same vendor: Dlink
CVE-2025-28398Same vendor: Dlink
CVE-2025-10123Same vendor: Dlink
CVE-2023-45575Same vendor: Dlink
CVE-2016-6563Same vendor: Dlink

Affected Assets

dlink
dir-300 firmware
≤ 1.06 · ≤ 2.06

Mitigating Controls

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

degrades

Network segmentation and routing policies reduce the chance that a mis-resolved name leads to an unintended external resource.

degrades

Segregated networks limit the blast radius when a name or reference resolves outside the intended control sphere.

blocks

Secure SDLC practices include design reviews that can catch incorrect name or reference handling before deployment.

blocks

A.8.26 only requires that security requirements (including those that could address name-resolution issues) be identified during development or acquisition; it does not itself enforce, implement, or stop exploitation of an incorrectly-resolved name or reference.

blocks

A.8.27 mandates security-by-design principles (least privilege, default-deny, distrust-external-input, security-oriented design reviews, hardening) that reach many but not all name-resolution mistakes; a bounded remainder (e.g. flawed resolution logic inside trusted components or libraries) can still be introduced and exploited.

prevents

Secure-coding standards directly address canonicalization, input validation and safe name resolution, mitigating CWE-706.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-706, a class-level weakness, and none of its children carries one either.

References