CVE-2024-0315VulnerabilityPublished 15 Jan 2024Updated 3 Jun 2025

CVE-2024-0315: FireEye Central Management · PHP Remote File Inclusion

Affects FireEye Central ManagementSource CVE Database V5

Not known to be exploited · CVSS 6.6 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.6Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
FireEye FireEye Central Management	Affected =9.1.1.956704	Fixed in–

AI-suggested

To mitigate this vulnerability, European organizations should prioritize upgrading FireEye Central Management to a patched version once available from the vendor. In the interim, strict access controls should be enforced to limit who can create reports or upload files within the system, reducing the risk of malicious file uploads. Implement application-level input validation and sanitization to prevent malicious filenames from being processed. Network segmentation should isolate the management system from less trusted networks and users. Monitoring and logging should be enhanced to detect unusual file upload activity or attempts to exploit the vulnerability. Additionally, organizations should conduct regular audits of user privileges to ensure that only trusted personnel have the necessary permissions to interact with report creation features. Employing web application firewalls (WAFs) with rules targeting file inclusion attacks may provide additional protection. Finally, organizations should prepare incident response plans specific to potential exploitation scenarios involving their FireEye infrastructure.

Description

Remote file inclusion vulnerability in FireEye Central Management affecting version 9.1.1.956704. This vulnerability allows an attacker to upload a malicious PDF file to the system during the report creation process.

Impact

For European organizations, the impact of this vulnerability can be substantial. FireEye Central Management is often deployed in security operations centers (SOCs) and used by enterprises, government agencies, and critical infrastructure operators to aggregate and analyze security alerts. Exploitation could lead to unauthorized access to sensitive security data, including threat intelligence and incident reports, compromising confidentiality. The partial integrity impact could allow attackers to manipulate reports or system behavior, potentially hiding malicious activity or disrupting incident response workflows. Availability impact, while limited, could still affect the timely operation of security monitoring. Given the local attack vector and required privileges, exploitation might be limited to insiders or attackers who have already gained some foothold, but the consequences of such exploitation in a security management context are severe. European organizations handling sensitive data or critical infrastructure are particularly at risk due to potential data breaches and operational disruptions.

CWE-98Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') (opens in a new tab)
Variant weaknessLikelihood of exploit: HighOWASP Top 10 A05:2025: Injection (opens in a new tab)
The PHP application receives input from an upstream component, but it does not restrict or incorrectly restricts the input before its usage in "require," "include," or similar functions.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Enforcement by Conversion
When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Vulnerable Dependency Management (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
OWASP ASVS 4.0.3
V12.3.3 (opens in a new tab)
V12.3.6 (opens in a new tab)
V14.2.3 (opens in a new tab)
Attack patterns
PHP Remote File Inclusion (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

incibe.es/en/incibe-cert/notices/aviso/multiple-vulnerabilities-fireeye-products (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Jul 2025, 20:25 UTC

WeaknessesCWE-98

Technical details

References

Community reviews

Related threats