Unauthenticated server access via undisclosed authentication flaw
Published Dec 25, 2023 · Updated Aug 2, 2024
Broken access control in Jamf Pro Server before 10.46.1 allows remote attackers to bypass authentication through network requests. Jamf identifies the affected locus only as an authentication implementation and has not disclosed which request or access-control decision is mishandled. No credentials or user interaction are required, but the public record does not specify the resources or operations exposed after bypass.
Summary
What happened
Broken access control in Jamf Pro Server before 10.46.1 allows remote attackers to bypass authentication through network requests. Jamf identifies the affected locus only as an authentication implementation and has not disclosed which request or access-control decision is mishandled. No credentials or user interaction are required, but the public record does not specify the resources or operations exposed after bypass.
The record
- CVE
- CVE-2023-31224
- Published
- Dec 25, 2023
- Updated
- Aug 2, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-287, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 25, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo