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

> Attackers can exploit a directory traversal flaw in Tamale RMS to enumerate sensitive contact information, including usernames and email addresses, stored on the host.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 5 Jun 2023
- **Updated:** 8 Jan 2025
- **Also known as:** GHSA-vv78-mf5r-v5q7

## What is CVE-2023-33524?

CVE-2023-33524 is a medium-severity path traversal vulnerability in n/a, published on 5 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Advent/SSC Inc. Tamale RMS < 23.1 is vulnerable to Directory Traversal. If one traverses to the affected URL, one enumerates Contact information on the host which contains usernames, e-mail addresses, and other internal information stored within the web app.

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

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

It affects 1 product.


Products: Advent Tamale Rms.

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

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

## Is CVE-2023-33524 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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