CVE-2019-17076
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 · uneditedAn issue was discovered in Jamf Pro 9.x and 10.x before 10.15.1. Deserialization of untrusted data when parsing JSON in several APIs may cause Denial of Service (DoS), remote code execution (RCE), and/or deletion of files on the Jamf Pro server.
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 versions 9.x and 10.x before 10.15.1 insecurely deserialize untrusted JSON data in multiple API endpoints, enabling remote attackers to potentially execute arbitrary code on the server or delete files.
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>= 9.4, <= 9.101.4>= 10.0.0, <= 10.15.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 versionLog into the Jamf Pro Admin Console and navigate to Settings > System Settings > About, or query the Jamf Pro server API at /JSSCheckVersion using: curl -k https://your-jamf-hostname/JSSCheckVersionAffected if The displayed version falls within 9.4 to 9.101.4, or 10.0.0 to 10.15.0 (inclusive)
-
Confirm Jamf Pro API endpoints are network-accessibleTest connectivity to common Jamf API ports from external locations: curl -k -o /dev/null -s -w '%{http_code}' https://your-jamf-hostname:8443/api/ (port 443 or 8443 are typical)Affected if HTTP 401/403 responses indicate the API is reachable; open internet exposure increases risk
-
Verify API JSON deserialization endpoints are activeSend a test JSON payload to known API endpoints such as /api/v1/computers or /api/v1/mobile-devices and inspect the response headers: curl -k -X POST https://your-jamf-hostname:8443/api/v1/computers -H 'Content-Type: application/json' -d '{}' -w '\n%{http_code}'Affected if The server accepts JSON content-type requests and returns API responses, indicating the vulnerable deserialization code path is active
-
Check for evidence of exploitation attempts in Jamf Pro logsReview Jamf Pro server logs located in /Library/Logs/Jamf or the Tomcat logs directory for deserialization-related errors or suspicious API activity patternsAffected if Log entries show deserialization exceptions, unexpected JSON structures, or API calls from unexpected sources
You are affected if your Jamf Pro version is 9.4 through 9.101.4 or 10.0.0 through 10.15.0 AND the API endpoints are network-accessible, since the insecure JSON deserialization flaw in those versions can be triggered remotely.
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.
dbcve · scopedUpgrade Jamf Pro to version 10.15.1 or later to remediate the deserialization vulnerability.
Jamf Pro 10.15.1 or later
- Backup the Jamf Pro database and configuration files before proceeding with any upgrade
- Review the official Jamf Pro upgrade documentation at resources.jamf.com for your current version
- Upgrade Jamf Pro to version 10.15.1 or later (for 9.x versions, you may need to first upgrade to a compatible 10.x version)
- After upgrade, verify the Jamf Pro services started successfully
- Confirm the deserialization vulnerability is resolved by testing the affected API endpoints
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.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 $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-17076 — 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-2019-17076 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