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

> Remote attackers can read arbitrary files via the Pic/Indexes interface in OfficeWeb365, exposing sensitive information.

- **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:** 10 Sep 2024
- **Updated:** 11 Sep 2024
- **Also known as:** GHSA-2h5m-ffc8-9ffr

## What is CVE-2024-37728?

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

### Official description

Arbitrary File Read vulnerability in Xi'an Daxi Information Technology Co., Ltd OfficeWeb365 v.7.18.23.0 and v8.6.1.0 allows a remote attacker to obtain sensitive information via the "Pic/Indexes" interface

Weakness: CWE-922 (Insecure Storage of Sensitive Information), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2024-37728 being exploited?

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

Public exploit code:

- OfficeWeb365 Indexs Interface - Arbitrary File Read (nuclei): http/cves/2024/CVE-2024-37728.yaml

## Fix prompt for AI coding agents

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

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

## Sources

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

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