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

> A guest can perform a path traversal attack to download personal information and view all files on the system due to missing permissions and path controls.

- **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:** 18 Oct 2023
- **Updated:** 13 Sep 2024
- **Also known as:** GHSA-pmmx-5xxg-mxh5

## What is CVE-2023-45383?

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

### Official description

In the module "SoNice etiquetage" (sonice_etiquetage) up to version 2.5.9 from Common-Services for PrestaShop, a guest can download personal information without restriction by performing a path traversal attack. Due to a lack of permissions control and a lack of control in the path name construction, a guest can perform a path traversal to view all files on the information system.

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

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

It affects 1 product.


Products: Common-Services Sonice Etiquetage.

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

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

## Is CVE-2023-45383 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-45383 is a high-severity path traversal vulnerability in n/a, published on 18 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-45383 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-45383/ (Markdown: https://insights.sbomify.com/CVE-2023-45383/index.md)
```

## Sources

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

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