# CVE-2024-0316: Improper cleanup vulnerability in FireEye Endpoint Security


- **Severity:** Medium 6.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 15 Jan 2024
- **Updated:** 1 Oct 2024
- **Also known as:** GHSA-359j-4p99-7w98

## What is CVE-2024-0316?

CVE-2024-0316 is a medium-severity vulnerability in FireEye Endpoint Security, published on 15 Jan 2024. 

### Official description

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.

Weakness: CWE-460 (Improper Cleanup on Thrown Exception)

## Which versions are affected by CVE-2024-0316?

It affects 1 product.


Products: Fireeye Endpoint Security.

## How do I fix CVE-2024-0316?

No fix has been published for CVE-2024-0316 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-0316 being exploited?

There is no known exploitation of CVE-2024-0316 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-0316 and fix it if it is affected.

What it is: CVE-2024-0316 is a medium-severity vulnerability in FireEye Endpoint Security, published on 15 Jan 2024. 
Exploitation: There is no known exploitation of CVE-2024-0316 in the wild and no public exploit code.

Affected product: FireEye Endpoint Security. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-0316/ (Markdown: https://insights.sbomify.com/CVE-2024-0316/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-0316
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-0316
- OSV: https://osv.dev/vulnerability/CVE-2024-0316

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-0316/
Summaries are generated and may contain mistakes; the official description above is the record.