# CVE-2024-8903: Privilege escalation in Acronis Cyber Protect Cloud Agent

> Local attackers can escalate privileges by manipulating active protection service settings due to unnecessary privilege assignments in the Acronis agent.

- **Severity:** Medium 4.7 (`CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2024
- **Updated:** 23 Sep 2024
- **Also known as:** GHSA-xr28-hrcf-5jw6

## What is CVE-2024-8903?

CVE-2024-8903 is a medium-severity vulnerability in Acronis Cyber Protect Cloud Agent, published on 23 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Local active protection service settings manipulation due to unnecessary privileges assignment. The following products are affected: Acronis Cyber Protect Cloud Agent (Windows, macOS) before build 38565.

Weakness: CWE-250 (Execution with Unnecessary Privileges)

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


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

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

## Is CVE-2024-8903 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-8903 is a medium-severity vulnerability in Acronis Cyber Protect Cloud Agent, published on 23 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-8903 in the wild and no public exploit code.

Affected product: Acronis Cyber Protect Cloud Agent. 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-8903/ (Markdown: https://insights.sbomify.com/CVE-2024-8903/index.md)
```

## Sources

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

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