# CVE-2024-0317: Cross-Site Scripting in FireEye EX

> An attacker can execute JavaScript via crafted parameters to steal session details from authenticated users of FireEye EX.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Jan 2024
- **Updated:** 3 Jun 2025
- **Also known as:** GHSA-g566-qqx6-fg4r

## What is CVE-2024-0317?

CVE-2024-0317 is a medium-severity cross-site scripting vulnerability in FireEye EX, published on 15 Jan 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cross-Site Scripting in FireEye EX, affecting version 9.0.3.936727. Exploitation of this vulnerability allows an attacker to send a specially crafted JavaScript payload via the 'type' and 's_f_name' parameters to an authenticated user to retrieve their session details.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 3 products.


Products: Fireeye Ex 3500 Firmware, Fireeye Ex 5500 Firmwarea, Fireeye Ex 8500 Firmware.

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

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

## Is CVE-2024-0317 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-0317 is a medium-severity cross-site scripting vulnerability in FireEye EX, published on 15 Jan 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-0317 in the wild and no public exploit code.

Affected product: FireEye EX. 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-0317/ (Markdown: https://insights.sbomify.com/CVE-2024-0317/index.md)
```

## Sources

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

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