# CVE-2024-45316: Path traversal in Connect Tunnel

> Standard users can delete arbitrary files via improper link resolution, potentially leading to local privilege escalation.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Oct 2024
- **Updated:** 11 Oct 2024
- **Also known as:** GHSA-6vwq-gg49-hj9w

## What is CVE-2024-45316?

CVE-2024-45316 is a high-severity path traversal vulnerability in SonicWall Connect Tunnel, published on 11 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Improper link resolution before file access ('Link Following') vulnerability in SonicWall Connect Tunnel (version 12.4.3.271 and earlier of Windows client) allows users with standard privileges to delete arbitrary folders and files, potentially leading to local privilege escalation attack.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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


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

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

## Is CVE-2024-45316 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-45316 is a high-severity path traversal vulnerability in SonicWall Connect Tunnel, published on 11 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-45316 in the wild and no public exploit code.

Affected product: SonicWall Connect Tunnel. 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-45316/ (Markdown: https://insights.sbomify.com/CVE-2024-45316/index.md)
```

## Sources

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

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