CVE-2023-31224
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 · uneditedThere is broken access control during authentication in Jamf Pro Server before 10.46.1.
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 confidenceBroken access control during authentication in Jamf Pro Server before version 10.46.1 allows unauthenticated attackers to bypass authentication mechanisms and gain unauthorized access to the MDM platform.
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.47.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.
-
Locate Jamf Pro installationCheck if Jamf Pro is running by accessing the Jamf Pro admin console URL (typically on port 8443 or 443) or check running services on the server for Java processes related to Jamf.Affected if Jamf Pro is accessible and running on the server
-
Identify installed Jamf Pro versionLog into the Jamf Pro admin console and navigate to Settings > System > About Jamf Pro, or access the /healthCheck.html endpoint which displays version information in the response headers or page content.Affected if The displayed version is below 10.47.0
-
Verify authentication configurationReview the Jamf Pro login page and attempt to access protected resources without credentials. Check if the login mechanism properly rejects unauthenticated requests.Affected if Unauthenticated access to MDM functions is possible or authentication can be bypassed
-
Check Jamf Pro logs for authentication anomaliesReview Jamf Pro logs in /var/log/jamf or through the admin console Logs section for failed authentication attempts, especially from unauthorized IP addresses or unusual patterns.Affected if Logs show successful authentication bypass attempts or unexpected unauthenticated access
A user is affected if Jamf Pro Server version is below 10.47.0 and authentication can be bypassed to gain unauthorized MDM access.
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 · scoped10.47.0
Upgrade Jamf Pro Server to version 10.46.1 or later to address the authentication bypass vulnerability.
Jamf Pro 10.47.0 or later
- 1. Back up the Jamf Pro database and all configuration files before proceeding with the upgrade.
- 2. Download Jamf Pro version 10.47.0 or later from the official Jamf resources portal at learn.jamf.com.
- 3. Follow Jamf's standard upgrade procedure: stop the Jamf Pro services, run the installer for the new version, and allow the database migration to complete.
- 4. Restart the Jamf Pro services and verify the application is functioning correctly.
- 5. Confirm the authentication vulnerability is resolved by testing user authentication flows and reviewing audit logs.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-31224 — 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-2023-31224 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