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

> Unauthenticated attackers can expose sensitive files via the download functionality in iDURAR applications.

- **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:** 4 Mar 2024
- **Updated:** 16 Aug 2024
- **Also known as:** GHSA-jqhq-7m2m-3xjx

## What is CVE-2024-25164?

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

### Official description

iA Path Traversal vulnerability exists in iDURAR v2.0.0, that allows unauthenticated attackers to expose sensitive files via the download functionality.

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

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

It affects 1 product.


Products: Idurarapp Idurar.

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

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

## Is CVE-2024-25164 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-27742](https://insights.sbomify.com/CVE-2023-27742/): SQL injection in n/a (critical 9.8)
- [CVE-2024-47769](https://insights.sbomify.com/CVE-2024-47769/): IDURAR has a Path Traversal (unauthenticated user can read sensitive data) (high 7.5)
- [CVE-2023-52265](https://insights.sbomify.com/CVE-2023-52265/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

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

## Sources

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

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