# CVE-2024-9845: Privilege escalation in Automation

> A local authenticated attacker can achieve privilege escalation due to insecure permissions in Ivanti Automation.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 11 Dec 2024
- **Updated:** 19 Dec 2024
- **Also known as:** GHSA-p8jq-vpfm-hqfj

## What is CVE-2024-9845?

CVE-2024-9845 is a high-severity vulnerability in Ivanti Automation, published on 11 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Under specific circumstances, insecure permissions in Ivanti Automation before version 2024.4.0.1 allows a local authenticated attacker to achieve local privilege escalation.

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 1 product.


Products: Ivanti Automation.

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

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

## Is CVE-2024-9845 being exploited?

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

## Other vulnerabilities in Ivanti Automation

- [CVE-2022-44569](https://insights.sbomify.com/CVE-2022-44569/): Auth bypass in Automation (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-9845 is a high-severity vulnerability in Ivanti Automation, published on 11 Dec 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-9845 in the wild and no public exploit code.

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

## Sources

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

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