CVE-2018-10465
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 · uneditedJamf Pro 10.x before 10.3.0 has Incorrect Access Control. Jamf Pro user accounts and groups with access to log in to Jamf Pro had full access to endpoints in the Universal API (UAPI), regardless of account privileges or privilege sets. An authenticated Jamf Pro account without required privileges could be used to perform CRUD actions (GET, POST, PUT, DELETE) on UAPI endpoints, which could result in unauthorized information disclosure, compromised data integrity, and data loss. For a full listing of available UAPI endpoints and associated CRUD actions you can navigate to /uapi/doc in your instance of Jamf Pro.
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 · high confidenceJamf Pro 10.x before 10.3.0 contains an Incorrect Access Control vulnerability in the Universal API (UAPI). Authenticated users with basic login access could perform full CRUD operations (GET, POST, PUT, DELETE) on UAPI endpoints regardless of their assigned privilege sets, allowing privilege escalation and unauthorized data access/modification.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 10.0.0, < 10.3.0CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 installed Jamf Pro versionAccess Jamf Pro Admin console and navigate to Settings > System > About, or run: grep -i version /Library/JSS/Config/jss_config.plist 2>/dev/nullAffected if The version is 10.0.0 through 10.2.x (any version >= 10.0.0 and < 10.3.0)
-
Verify UAPI endpoint accessibilityAttempt to access a UAPI endpoint (e.g., /uapi/auth) using an account with Basic privileges via curl or API client: curl -k -u basicuser:password https://yourjamfserver:8443/uapi/authAffected if The request returns a successful response rather than a 403 Forbidden, indicating UAPI is accessible without proper privilege enforcement
-
Confirm user privilege assignmentIn Jamf Pro Admin, go to Users > User Accounts and verify a test account is assigned to a limited privilege set (e.g., Auditor or Custom with restricted permissions)Affected if A user with limited privileges can successfully execute GET, POST, PUT, or DELETE operations on UAPI endpoints they should not have access to
-
Review UAPI access logsIn Jamf Pro, navigate to Management Settings > System > API Status and Logging, or inspect /var/log/jss.log for UAPI activity. Search for operations performed by users with basic-level rolesAffected if Logs show CRUD operations from basic users on endpoints outside their assigned privilege scope
You are affected if Jamf Pro version is 10.0.0 through 10.2.x AND the UAPI is accessible to users with basic privilege sets who can perform operations beyond their intended permissions.
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 data10.3.0
Upgrade Jamf Pro to version 10.3.0 or later to remediate the access control bypass. Review UAPI access logs for suspicious activity from affected versions.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-10465 — 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-2018-10465 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