# CVE-2024-34471: Path traversal in n/a

> An attacker can exploit a path traversal flaw in HSC Mailinspector to read and delete arbitrary files on the server, potentially disrupting email services.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **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:** 6 May 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-x7hx-9w3p-f5r3

## What is CVE-2024-34471?

CVE-2024-34471 is a medium-severity path traversal vulnerability in n/a, published on 6 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in HSC Mailinspector 5.2.17-3. A Path Traversal vulnerability (resulting in file deletion) exists in the mliRealtimeEmails.php file. The filename parameter in the export HTML functionality does not properly validate the file location, allowing an attacker to read and delete arbitrary files on the server. This was observed when the mliRealtimeEmails.php file itself was read and subsequently deleted, resulting in a 404 error for the file and disruption of email information loading.

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

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

It affects 1 product.


Products: Hsclabs Mailinspector.

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

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

## Is CVE-2024-34471 being exploited?

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

Public exploit code:

- https://github.com/osvaldotenorio/CVE-2024-34471 (github_poc): https://github.com/osvaldotenorio/CVE-2024-34471

## Other vulnerabilities in n/a

- [CVE-2024-32370](https://insights.sbomify.com/CVE-2024-32370/): Information disclosure in n/a (critical 9.8)
- [CVE-2024-34470](https://insights.sbomify.com/CVE-2024-34470/): Path traversal in n/a (high 8.6)
- [CVE-2026-29962](https://insights.sbomify.com/CVE-2026-29962/): Path traversal in n/a (high 7.5)
- [CVE-2026-29963](https://insights.sbomify.com/CVE-2026-29963/): Path traversal in n/a (high 7.5)
- [CVE-2024-32371](https://insights.sbomify.com/CVE-2024-32371/): Privilege escalation in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-34471 is a medium-severity path traversal vulnerability in n/a, published on 6 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-34471 exists.

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-2024-34471/ (Markdown: https://insights.sbomify.com/CVE-2024-34471/index.md)
```

## Sources

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

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