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

> Unauthenticated attackers can read arbitrary sensitive files via directory traversal in the log download script of Carel pCOWeb HVAC Gateways.

- **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:** 31 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-wwr2-w2jp-vx63

## What is CVE-2022-37122?

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

### Official description

Carel pCOWeb HVAC BACnet Gateway 2.1.0, Firmware: A2.1.0 - B2.1.0, Application Software: 2.15.4A Software v16 13020200 suffers from an unauthenticated arbitrary file disclosure vulnerability. Input passed through the 'file' GET parameter through the 'logdownload.cgi' Bash script is not properly verified before being used to download log files. This can be exploited to disclose the contents of arbitrary and sensitive files via directory traversal attacks.

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

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

It affects 3 products.


Products: Carel Applica, Carel Pcoweb Card Firmware, Carel Pcoweb Hvac Bacnet Gateway.

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

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

## Is CVE-2022-37122 being exploited?

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

Public exploit code:

- CVE-2022-37122 Path Traversal Scanner (github_poc): https://github.com/bughuntar/CVE-2022-37122-Exploit
- Carel pCOWeb HVAC BACnet Gateway 2.1.0 - Path Traversal (nuclei): http/cves/2022/CVE-2022-37122.yaml

## Fix prompt for AI coding agents

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

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

## Sources

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

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