# CVE-2024-22398: Path traversal in Email Security

> Remote administrators can delete arbitrary files from the SonicWall Email Security Appliance via a path traversal vulnerability.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Mar 2024
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-ccj3-7f9q-8jw9

## What is CVE-2024-22398?

CVE-2024-22398 is a medium-severity path traversal vulnerability in SonicWall Email Security, published on 14 Mar 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An improper Limitation of a Pathname to a Restricted Directory (Path Traversal) vulnerability in SonicWall Email Security Appliance could allow a remote attacker with administrative privileges to conduct a directory traversal attack and delete arbitrary files from the appliance file system.

Weakness: CWE-23 (Relative Path Traversal), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2024-22398 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-22398 is a medium-severity path traversal vulnerability in SonicWall Email Security, published on 14 Mar 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-22398 exists.

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

## Sources

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

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