# CVE-2024-4395: Lack of Client Validation in Jamf Compliance Editor's Helper Service May Result in Privilege Escalation

> Local attackers can escalate privileges via the XPC service in Jamf Compliance Editor on macOS due to lack of client validation.

- **Severity:** High 7.3 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/S:N/AU:N/R:U/V:D/RE:M/U:Green`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Jun 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-68wq-r58h-5q45

## What is CVE-2024-4395?

CVE-2024-4395 is a high-severity vulnerability in Jamf Compliance Editor, published on 27 Jun 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The XPC service within the audit functionality of Jamf Compliance Editor before version 1.3.1 on macOS can lead to local privilege escalation.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2024-4395 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-4395 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-4395 is a high-severity vulnerability in Jamf Compliance Editor, published on 27 Jun 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-4395 exists.

Affected product: Jamf Compliance Editor. 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-4395/ (Markdown: https://insights.sbomify.com/CVE-2024-4395/index.md)
```

## Sources

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

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