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

> Attackers can download arbitrary files and access sensitive information via a crafted request in NUS-M9 ERP Management Software.

- **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 Nov 2024
- **Updated:** 21 Nov 2024
- **Also known as:** GHSA-cgqw-4mgw-89pm

## What is CVE-2024-44757?

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

### Official description

An arbitrary file download vulnerability in the component /Basics/DownloadInpFile of NUS-M9 ERP Management Software v3.0.0 allows attackers to download arbitrary files and access sensitive information via a crafted interface request.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Nuserp Nus-M9 Erp.

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

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

## Is CVE-2024-44757 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-44756](https://insights.sbomify.com/CVE-2024-44756/): SQL injection in n/a (critical 9.8)
- [CVE-2024-44758](https://insights.sbomify.com/CVE-2024-44758/): File upload in n/a (critical 9.8)
- [CVE-2024-44759](https://insights.sbomify.com/CVE-2024-44759/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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