# CVE-2023-46315: Path traversal in n/a

> Attackers can read arbitrary local files via path traversal if Gradio authentication is enabled without a secret key, exposing sensitive data.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Oct 2023
- **Updated:** 12 Sep 2024
- **Also known as:** GHSA-jq2h-j9qf-53rv

## What is CVE-2023-46315?

CVE-2023-46315 is a high-severity path traversal vulnerability in n/a, published on 22 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The zanllp sd-webui-infinite-image-browsing (aka Infinite Image Browsing) extension before 977815a for stable-diffusion-webui (aka Stable Diffusion web UI), if Gradio authentication is enabled without secret key configuration, allows remote attackers to read any local file via /file?path= in the URL, as demonstrated by reading /proc/self/environ to discover credentials.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2023-46315?

It affects 1 product.


Products: Zanllp Stable Diffusion Webui Infinite Image Browsing.

## How do I fix CVE-2023-46315?

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

## Is CVE-2023-46315 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-46315 and fix it if it is affected.

What it is: CVE-2023-46315 is a high-severity path traversal vulnerability in n/a, published on 22 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-46315 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-2023-46315/ (Markdown: https://insights.sbomify.com/CVE-2023-46315/index.md)
```

## Sources

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

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