Browser script execution via inventory history
Published Apr 2, 2021 · Updated Aug 3, 2024
Cross-site scripting in Jamf Pro before 10.28.0 allows remote attackers to alter browser content via inventory history content. Jamf has not published the affected field, rendering path, or missing output-encoding operation, so the injection mechanism remains undisclosed. Exploitation requires a user to view the affected history content, and script execution is limited to that user's browser context rather than the server host.
Summary
What happened
Cross-site scripting in Jamf Pro before 10.28.0 allows remote attackers to alter browser content via inventory history content. Jamf has not published the affected field, rendering path, or missing output-encoding operation, so the injection mechanism remains undisclosed. Exploitation requires a user to view the affected history content, and script execution is limited to that user's browser context rather than the server host.
The record
- CVE
- CVE-2021-30125
- Published
- Apr 2, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 2, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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.
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.
Weakness, pattern, technique
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