# CVE-2022-37681: Path traversal in n/a

> Attackers can perform directory traversal via crafted GET requests to read arbitrary files from Hitachi monitoring system devices.

- **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:** 29 Aug 2022
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-j2h4-q276-rg48

## What is CVE-2022-37681?

CVE-2022-37681 is a high-severity path traversal vulnerability in n/a, published on 29 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Hitachi Kokusai Electric Newtork products for monitoring system (Camera, Decoder and Encoder) and below allows attckers to perform a directory traversal via a crafted GET request to the endpoint /ptippage.cgi. Security information ID hitachi-sec-2022-001 contains fixes for the issue.

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

## Which versions are affected by CVE-2022-37681?

It affects 1 product.


Products: Hitachi Hc-Ip9100hd Firmware.

## How do I fix CVE-2022-37681?

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

## Is CVE-2022-37681 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-37680](https://insights.sbomify.com/CVE-2022-37680/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-37681 and fix it if it is affected.

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

## Sources

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

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