# CVE-2024-3318: SailPoint Identity Security Cloud Connector File Path Traversal Vulnerability

> An authenticated administrator can exploit path traversal to access files uploaded for other sources in SailPoint Identity Security Cloud.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 May 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-j5rg-hrw2-2gf7

## What is CVE-2024-3318?

CVE-2024-3318 is a medium-severity path traversal vulnerability in SailPoint Identity Security Cloud, published on 15 May 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

A file path traversal vulnerability was identified in the DelimitedFileConnector Cloud Connector that allowed an authenticated administrator to set arbitrary connector attributes, including the “file“ attribute, which in turn allowed the user to access files uploaded for other sources.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2024-3318 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-3318 is a medium-severity path traversal vulnerability in SailPoint Identity Security Cloud, published on 15 May 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-3318 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-3318/ (Markdown: https://insights.sbomify.com/CVE-2024-3318/index.md)
```

## Sources

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

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