# CVE-2024-48735: Path traversal in n/a

> Remote attackers can access internal files via directory traversal in SAS Studio, though the vendor disputes this as intended behavior for authorized users.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Oct 2024
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-mpp2-2v83-ccjm

## What is CVE-2024-48735?

CVE-2024-48735 is a high-severity path traversal vulnerability in n/a, published on 30 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Directory Traversal in /SASStudio/sasexec/sessions/{sessionID}/workspace/{InternalPath} in SAS Studio 9.4 allows remote attacker to access internal files by manipulating default path during file download. NOTE: this is disputed by the vendor because these filesystem paths are allowed for authorized users.

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

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


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

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

## Is CVE-2024-48735 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-48735 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-48735 is a high-severity path traversal vulnerability in n/a, published on 30 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-48735 exists.

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-2024-48735/ (Markdown: https://insights.sbomify.com/CVE-2024-48735/index.md)
```

## Sources

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

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