# CVE-2025-0617: Denial of service in Trellix HX Console

> An attacker can cause a Denial of Service in Trellix HX Console by sending specially crafted data that triggers exponential entity expansions during file parsing.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jan 2025
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-cf2r-vpqc-55g6

## What is CVE-2025-0617?

CVE-2025-0617 is a medium-severity denial of service vulnerability in Trellix HX Console, published on 29 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An attacker with access to an HX 10.0.0  and previous versions, may send specially-crafted data to the HX console.  The malicious detection would then trigger file parsing containing exponential entity expansions in the consumer process thus causing a Denial of Service.

Weakness: CWE-776 (Improper Restriction of Recursive Entity References in DTDs)

## Which versions are affected by CVE-2025-0617?


## How do I fix CVE-2025-0617?

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

## Is CVE-2025-0617 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-0617 and fix it if it is affected.

What it is: CVE-2025-0617 is a medium-severity denial of service vulnerability in Trellix HX Console, published on 29 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0617 in the wild and no public exploit code.

Affected product: Trellix HX Console. 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-2025-0617/ (Markdown: https://insights.sbomify.com/CVE-2025-0617/index.md)
```

## Sources

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

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