# CVE-2022-44796: Weak cryptography in n/a

> Weak JWT secret generation allows attackers to forge tokens and gain unauthorized access to the Web UI.

- **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:** 7 Nov 2022
- **Updated:** 1 May 2025
- **Also known as:** GHSA-39pq-3mh9-m5qg

## What is CVE-2022-44796?

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

### Official description

An issue was discovered in Object First Ootbi BETA build 1.0.7.712. The authorization service has a flow that allows getting access to the Web UI without knowing credentials. For signing, the JWT token uses a secret key that is generated through a function that doesn't produce cryptographically strong sequences. An attacker can predict these sequences and generate a JWT token. As a result, an attacker can get access to the Web UI. This is fixed in Object First Ootbi BETA build 1.0.13.1611.

Weakness: CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG))

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

It affects 1 product.


Products: Objectfirst Ootbi.

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

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

## Is CVE-2022-44796 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-44794](https://insights.sbomify.com/CVE-2022-44794/): Command injection in n/a (high 8.8)
- [CVE-2022-44795](https://insights.sbomify.com/CVE-2022-44795/): Weak cryptography in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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