# CVE-2021-35037: Open redirect in n/a

> An attacker can craft a malicious URL that redirects users to arbitrary external sites, potentially facilitating phishing attacks against Jamf Pro users.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Jul 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-mpmp-43vw-64c6

## What is CVE-2021-35037?

CVE-2021-35037 is a medium-severity vulnerability in n/a, published on 12 Jul 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2021-35037?

It affects 1 product.


Products: Jamf Jamf.

## How do I fix CVE-2021-35037?

No fix has been published for CVE-2021-35037 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-35037 being exploited?

There is no known exploitation of CVE-2021-35037 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2023-31224](https://insights.sbomify.com/CVE-2023-31224/): Auth bypass in n/a (critical 9.8)
- [CVE-2021-39303](https://insights.sbomify.com/CVE-2021-39303/): Server-side request forgery in n/a (critical 9.8)
- [CVE-2019-17076](https://insights.sbomify.com/CVE-2019-17076/): Deserialization in n/a (critical 9.8)
- [CVE-2021-40809](https://insights.sbomify.com/CVE-2021-40809/): Privilege escalation in n/a (high 8.8)
- [CVE-2018-10465](https://insights.sbomify.com/CVE-2018-10465/): Missing authorization in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-35037 and fix it if it is affected.

What it is: CVE-2021-35037 is a medium-severity vulnerability in n/a, published on 12 Jul 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-35037 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-35037/ (Markdown: https://insights.sbomify.com/CVE-2021-35037/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-35037
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-35037
- OSV: https://osv.dev/vulnerability/CVE-2021-35037

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-35037/
Summaries are generated and may contain mistakes; the official description above is the record.