# CVE-2022-37109: Auth bypass in n/a

> Attackers can bypass authentication and access sensitive files by exploiting improper access control and cookie secret generation in the camp application.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Nov 2022
- **Updated:** 1 May 2025
- **Also known as:** GHSA-hjg8-7hr5-c9j8

## What is CVE-2022-37109?

CVE-2022-37109 is a critical authentication bypass vulnerability in n/a, published on 14 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

patrickfuller camp up to and including commit bbd53a256ed70e79bd8758080936afbf6d738767 is vulnerable to Incorrect Access Control. Access to the password.txt file is not properly restricted as it is in the root directory served by StaticFileHandler and the Tornado rule to throw a 403 error when password.txt is accessed can be bypassed. Furthermore, it is not necessary to crack the password hash to authenticate with the application because the password hash is also used as the cookie secret, so an attacker can generate his own authentication cookie.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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

It affects 1 product.


Products: Camp Project Camp.

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

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

## Is CVE-2022-37109 being exploited?

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

Public exploit code:

- _camp_ Raspberry Pi camera server 1.0 -  Authentication Bypass (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-37109 is a critical authentication bypass vulnerability in n/a, published on 14 Nov 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-37109 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-37109/ (Markdown: https://insights.sbomify.com/CVE-2022-37109/index.md)
```

## Sources

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

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