Security readout for executives and security teams
Plain-English summary
CVE-2021-35037 is an open redirect issue in on-premises Jamf Pro before 10.30.1. A crafted link can look like it belongs to a trusted Jamf Pro instance but send the user to another, potentially malicious site. The main business risk is phishing and credential theft support, not direct server takeover.
Executive priority
Prioritize remediation for on-premises Jamf Pro because the issue can make phishing more credible using trusted infrastructure. Treat it as moderate urgency unless local evidence shows targeted phishing or exposed outdated instances.
Technical view
The CVE describes an unvalidated URL redirect in Jamf Pro before 10.30.1, limited by the description to customer-hosted on-premises environments. Jamf tracks it as PI-009822. The source bundle provides no CVSS score, CWE, technical root-cause detail, or exploit procedure.
Likely exposure
Organizations running on-premises Jamf Pro versions earlier than 10.30.1 are the stated exposure group. The provided sources do not identify Jamf Cloud, other Jamf products, or specific configurations as affected.
Exploitation context
The CVE is not listed as KEV in the supplied bundle, and no cited source states active exploitation. Practical abuse would likely depend on convincing a user to click a crafted Jamf-looking URL.
Researcher notes
Evidence is limited. The bundle names the affected version boundary and vulnerability class but omits CVSS, CWE, detailed affected CPEs, and proof of exploitation. Avoid assuming impact beyond open redirect-enabled social engineering.
Mitigation direction
- Upgrade on-premises Jamf Pro to 10.30.1 or later.
- Review Jamf release notes and security guidance for PI-009822.
- Warn administrators about Jamf-looking links that redirect externally.
- Use email and web filtering to reduce phishing delivery risk.
Validation and detection
- Inventory all Jamf Pro instances and confirm their versions.
- Confirm whether each Jamf Pro environment is on-premises or hosted.
- Check proxy or web logs for Jamf URLs leading to unexpected domains.
- Verify remediation status against Jamf Pro 10.30.1 release guidance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2021-35037 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://www.jamf.com/resources/product-documentation/jamf-pro-release-notes/CVE reference · x_refsource_MISC
- https://www.jamf.com/jamf-nation/discussions/39219/jamf-pro-10-30-1-security-upgradeCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.