# CVE-2023-3701: Relative path traversal in Aqua eSolutions

> Authenticated users can exploit relative path traversal to access or modify other users' resources and platform configuration files.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **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:** 4 Oct 2023
- **Updated:** 19 Sep 2024
- **Also known as:** GHSA-9rjr-9f35-j89h

## What is CVE-2023-3701?

CVE-2023-3701 is a critical path traversal vulnerability in Aqua Drive, published on 4 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Aqua Drive, in its 2.4 version, is vulnerable to a relative path traversal vulnerability. By exploiting this vulnerability, an authenticated non privileged user could access/modify stored resources of other users. It could also be possible to access and modify the source and configuration files of the cloud disk platform, affecting the integrity and availability of the entire platform.

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

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

It affects 1 product.


Products: Aquaesolutions Aqua Drive.

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

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

## Is CVE-2023-3701 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-3701 is a critical path traversal vulnerability in Aqua Drive, published on 4 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-3701 in the wild and no public exploit code.

Affected product: Aqua Drive. 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-3701/ (Markdown: https://insights.sbomify.com/CVE-2023-3701/index.md)
```

## Sources

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

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