CVE-2024-5298
Dlink D-View 8 2.0.1.28
Raw vector
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2024-5298 is a high-severity Exposed Dangerous Method or Function (CWE-749) vulnerability in Dlink D-View 8. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 23% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
D-Link D-View contains a remote code execution vulnerability tracked as CVE-2024-5298 in the queryDeviceCustomMonitorResult method. The flaw stems from an exposed dangerous method that permits arbitrary code execution in the context of the root user on affected installations. Authentication is required to reach the method, yet the existing controls can be bypassed. The issue was assigned ZDI-CAN-21842 and carries a CVSS 3.0 score of 8.8.
Remote attackers who can reach the D-View instance may exploit the bypass to invoke the dangerous method and run code without further user interaction. Successful exploitation grants full control over the target system under root privileges.
The issue was publicly detailed in Zero Day Initiative advisory ZDI-24-449, which identifies the affected component and provides the technical description used for this summary. No separate vendor patch information appears in the referenced materials.
EPSS scores remained low, moving from a current value of 0.0410 to a peak of only 0.0625 before receding, indicating limited observed exploitation interest after disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-46534
Vulnerability Data
D-Link D-View queryDeviceCustomMonitorResult Exposed Dangerous Method Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of D-Link D-View. Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be bypassed.…
more
The specific flaw exists within the queryDeviceCustomMonitorResult method. The issue results from an exposed dangerous method. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-21842.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 4 hardening rules · 2 OS baselines
V8.2.1
Mitigating Controls (NIST 800-53 r5) AI
Access enforcement directly stops unauthorized callers from invoking dangerous API methods or functions.
Least privilege restricts which users or processes may reach dangerous methods, limiting exposure.
Least functionality removes or disables non-essential dangerous methods from the exposed interface altogether.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Enforcing least-privilege authorization directly prevents unrestricted dangerous API methods.
Secure SDLC practices stop developers from exposing dangerous functions in the first place.
Vulnerability identification processes will surface exposed dangerous methods during assessment.
Logical access controls at the network/environment layer can limit reachability of exposed functions.
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.
Security testing can detect exposed dangerous functions, but does not prevent their initial introduction.
Restricting privileged utility programs reduces exposure of dangerous functions, but does not eliminate the underlying weakness.
Privileged access rights limit who can invoke dangerous methods, but do not address whether the method itself should exist.
Secure development life cycle requires removal or protection of dangerous APIs during design and coding.
Application security requirements can mandate that dangerous methods are not exposed in interfaces.
Secure architecture principles discourage exposing dangerous functions, but do not guarantee their absence.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Ubuntu 22.04 (3 rules)
- V-260559 Ubuntu 22.04 LTS must ensure only users who need access to security functions are part of sudo group. prevents CWE-749
- V-260529 Ubuntu 22.04 LTS must be configured so that remote X connections are disabled, unless to fulfill documented and validated mission requirements. prevents CWE-749
- V-260557 Ubuntu 22.04 LTS must be configured to use AppArmor. prevents CWE-749
Ubuntu 24.04 (1 rule)
- V-270748 Ubuntu 24.04 LTS must ensure only users who need access to security functions are part of sudo group. prevents CWE-749