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

> Attackers can read arbitrary files from the server via directory traversal in the scan_folder parameter of eNMS.

- **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:** 20 Sep 2024
- **Updated:** 23 Sep 2024
- **Also known as:** GHSA-6q3p-cf37-rf5w

## What is CVE-2024-46648?

CVE-2024-46648 is a high-severity path traversal vulnerability in n/a, published on 20 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

eNMS 4.4.0 to 4.7.1 is vulnerable to Directory Traversal via scan_folder.

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

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

It affects 1 product.


Products: Enms Enms.

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

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

## Is CVE-2024-46648 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-11664](https://insights.sbomify.com/CVE-2024-11664/): eNMS TGZ File controller.py multiselect_filtering path traversal (high 8.7)
- [CVE-2024-46645](https://insights.sbomify.com/CVE-2024-46645/): Path traversal in n/a (high 7.5)
- [CVE-2024-46649](https://insights.sbomify.com/CVE-2024-46649/): Path traversal in n/a (high 7.5)
- [CVE-2024-46644](https://insights.sbomify.com/CVE-2024-46644/): Path traversal in n/a (medium 6.5)
- [CVE-2024-46646](https://insights.sbomify.com/CVE-2024-46646/): Path traversal in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-46648 is a high-severity path traversal vulnerability in n/a, published on 20 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-46648 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-46648/ (Markdown: https://insights.sbomify.com/CVE-2024-46648/index.md)
```

## Sources

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

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