Security Resilience

CVE-2024-0316

Fireeye Endpoint Security 5.2.0.958244

Published
15 January 2024
Modified
21 November 2024
CVSS Score v3.1 6.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
EPSS Score 0.0032 23th percentile
Risk Priority 51 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-2024-0316 is a medium-severity Improper Cleanup on Thrown Exception (CWE-460) vulnerability in Fireeye Endpoint Security. Its CVSS base score is 6.8 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Junk Data (T1001.001); ranked at the 23th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-24 (Fail in Known State) and SI-17 (Fail-safe Procedures) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Improper cleanup vulnerability in exceptions thrown in FireEye Endpoint Security, affecting version 5.2.0.958244. This vulnerability could allow an attacker to send multiple request packets to the containment_notify/preview parameter, which could lead to a service outage.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001.001 Junk Data Command And Control
Adversaries may add junk data to protocols used for command and control to make detection more difficult.
T1001.003 Protocol or Service Impersonation Command And Control
Adversaries may impersonate legitimate protocols or web service traffic to disguise command and control activity and thwart analysis efforts.
T1003.007 Proc Filesystem Credential Access
Adversaries may gather credentials from the proc filesystem or `/proc`.
T1007 System Service Discovery Discovery
Adversaries may try to gather information about registered local system services.
T1008 Fallback Channels Command And Control
Adversaries may use fallback or alternate communication channels if the primary channel is compromised or inaccessible in order to maintain reliable command and control and to avoid data transfer thresholds.
T1010 Application Window Discovery Discovery
Adversaries may attempt to get a listing of open application windows.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-32439Shared CWE-460
CVE-2025-30157Shared CWE-460
CVE-2023-46393Shared CWE-460
CVE-2026-93710Shared CWE-460
CVE-2026-33481Shared CWE-460
CVE-2026-20118Shared CWE-460
CVE-2025-69652Shared CWE-460
CVE-2024-20354Shared CWE-460
CVE-2025-59399Shared CWE-460
CVE-2024-0320Same vendor: Fireeye

Affected Assets

fireeye
endpoint security
5.2.0.958244

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Requires the system to fail to a known state on indicated failures, directly forcing proper state cleanup instead of leaving inconsistent state after an exception.

Mandates explicit fail-safe procedures on failures, which structurally enforces cleanup actions that the weakness omits.

Requires application of security engineering principles (e.g., fail-safe, complete mediation) during design that would eliminate improper exception cleanup.

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.

PR.PS-06 partial match
blocks

Secure SDLC practices directly enforce proper exception handling and resource cleanup.

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.

removes
blocks

Secure SDLC mandates exception-handling and cleanup practices that reduce improper state after thrown exceptions.

blocks

A.8.26 requires identifying and specifying security requirements (including resilience against attacks like SQL injection) during development or acquisition; it does not itself implement exception handling or cleanup logic that would stop CWE-460 from being exploitable.

blocks

A.8.27 mandates establishing and applying secure engineering principles (including secure-by-design, least privilege, fail-securely, and design reviews) but does not itself stop an exception-cleanup defect from being introduced in code or from being exploitable once present; the weakness can still be exploited.

References