# CVE-2024-3319: Security implication in SailPoint Identity Security Cloud IdentityProfile API Endpoints

> Authenticated administrators can execute arbitrary code via user-defined templates in IdentityProfile API endpoints, leading to remote code execution on the host.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 May 2024
- **Updated:** 16 Aug 2024
- **Also known as:** GHSA-c24r-pxmj-hx9h

## What is CVE-2024-3319?

CVE-2024-3319 is a critical code injection vulnerability in SailPoint Identity Security Cloud, published on 15 May 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An issue was identified in the Identity Security Cloud (ISC) Transform preview and IdentityProfile preview API endpoints that allowed an authenticated administrator to execute user-defined templates as part of attribute transforms which could allow remote code execution on the host.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2024-3319?


## How do I fix CVE-2024-3319?

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

## Is CVE-2024-3319 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-3319 and fix it if it is affected.

What it is: CVE-2024-3319 is a critical code injection vulnerability in SailPoint Identity Security Cloud, published on 15 May 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-3319 in the wild and no public exploit code.

Affected product: SailPoint Identity Security Cloud. 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-2024-3319/ (Markdown: https://insights.sbomify.com/CVE-2024-3319/index.md)
```

## Sources

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

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