CVE-2023-31224: There is broken access control during authentication in Jamf Pro Server before 10.46.1.
CVE-2023-31224 is a critical-severity flaw (CVSS 9.8) affecting jamf. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
There is broken access control during authentication in Jamf Pro Server before 10.46.1.
Why this priority
- Critical severity
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 9.8 (Critical) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 0.6% (top 52%) |
| CISA exploited list | No |
| Weakness | CWE-287 |
| Published | 2023-12-25 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2023-31224?
jamf: upgrade to 10.47.0. Exact commands for each OS are on this page.
Is CVE-2023-31224 being exploited?
CVE-2023-31224 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2023-31224 affect?
CVE-2023-31224 affects jamf. Severity is critical (CVSS 9.8). There is broken access control during authentication in Jamf Pro Server before 10.46.1.
How urgent is CVE-2023-31224?
Priority 51/100. Critical severity; Remotely exploitable, no login, no user action