# CVE-2024-4843: Missing authorization in ePolicy Orchestrator

> A least-privileged user can manipulate client tasks and assignments via insecure direct object references, leading to privilege escalation in Trellix ePolicy Orchestrator.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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:** 16 May 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-7v3w-v3wv-vhx2

## What is CVE-2024-4843?

CVE-2024-4843 is a medium-severity missing authorization vulnerability in Trellix ePolicy Orchestrator, published on 16 May 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

ePO doesn't allow a regular privileged user to delete tasks or assignments. Insecure direct object references that allow a least privileged user to manipulate the client task and client task assignments, hence escalating his/her privilege.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2024-4843 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-4843 is a medium-severity missing authorization vulnerability in Trellix ePolicy Orchestrator, published on 16 May 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-4843 in the wild and no public exploit code.

Affected product: Trellix ePolicy Orchestrator. 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-4843/ (Markdown: https://insights.sbomify.com/CVE-2024-4843/index.md)
```

## Sources

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

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