# CVE-2024-36857: Jan path traversal vulnerability

> An attacker can read arbitrary files from the server via the readFileSync interface in the Jan library.

- **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 Jun 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-5jqc-qj57-4hrc

## What is CVE-2024-36857?

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

### Official description

Jan v0.4.12 was discovered to contain an arbitrary file read vulnerability via the /v1/app/readFileSync interface.

Weakness: CWE-31 (Path Traversal: 'dir\..\..\filename')

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

2 open source packages ship an affected version, including @janhq/core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@janhq/core` | npm | All versions to 0.1.11 | None |
| `@janhq/core` | npm | All versions to 0.1.11 | None |

Products: Homebrew Jan.

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

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

## Is CVE-2024-36857 being exploited?

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

Public exploit code:

- Jan v0.4.12 'readFileSync' - Path Traversal (nuclei): http/cves/2024/CVE-2024-36857.yaml

## Other vulnerabilities in n/a

- [CVE-2024-36858](https://insights.sbomify.com/CVE-2024-36858/): Jan path traversal vulnerability (critical 9.8)
- [CVE-2024-37273](https://insights.sbomify.com/CVE-2024-37273/): Jan path traversal vulnerability (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-36857 is a high-severity path traversal vulnerability in n/a, published on 4 Jun 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-36857 exists.

Affected packages and fixed versions:
- @janhq/core (npm): affected all versions up to 0.1.11; no fix listed
- @janhq/core (npm): affected all versions up to 0.1.11; no fix listed

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

## Sources

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

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