CVE-2024-10183
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability in Jamf Pro's Jamf Remote Assist tool allows a local, non-privileged user to escalate their privileges to root on MacOS systems.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA local privilege escalation vulnerability exists in Jamf Pro's Jamf Remote Assist tool on macOS systems. An authenticated, non-privileged local user can exploit insufficient access controls or improper privilege handling within the Remote Assist component to gain root-level privileges on the affected system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:L/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Jamf Pro is installedRun 'ls /Applications/Jamf Pro.app' or check for /Library/Application Support/Jamf directory. Also run 'defaults read /Library/Preferences/com.jamfsoftware.jamfpro appVersion' to get the version number.Affected if Jamf Pro is installed and the version matches the vulnerable version range for this CVE.
-
Verify Jamf Remote Assist component presenceCheck for the presence of Remote Assist by examining /Library/Application Support/Jamf/RemoteAssist/ or running 'ls /Library/Application Support/Jamf/' to list Jamf components.Affected if The Remote Assist directory or component exists on the system.
-
Check if Jamf Remote Assist service is runningRun 'ps aux | grep -i "remoteassist"' or 'launchctl list | grep -i jamf' to identify if the Remote Assist service daemon is active.Affected if The Remote Assist service is currently running on the system.
-
Inspect file permissions on Remote Assist componentsRun 'ls -la /Library/Application Support/Jamf/RemoteAssist/' and check for world-writable or group-writable permissions on executables, scripts, or configuration files.Affected if Remote Assist files or scripts have overly permissive write access for standard users.
-
Audit for unauthorized root-level processesRun 'ps -ef | grep -v root | grep -i jamf' to identify Jamf processes running under non-root accounts, and check for unexpected root-owned processes spawned from user contexts.Affected if Non-privileged users have spawned processes that are executing with elevated root privileges through Jamf components.
A user is affected if Jamf Pro with Remote Assist is installed, the Remote Assist component or service is present and enabled, and the installed version falls within the vulnerable version range for CVE-2024-10183.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the vendor-supplied security update for Jamf Pro that addresses this vulnerability. Additionally, limit local user access to systems running Jamf Remote Assist and monitor for unauthorized privilege escalation attempts.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-10183 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-10183 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data