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

> An attacker with credentials can predict support bundle URLs due to insecure RNG, leading to local information disclosure of system logs.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Nov 2022
- **Updated:** 1 May 2025
- **Also known as:** GHSA-fxhg-25q8-4697

## What is CVE-2022-44795?

CVE-2022-44795 is a medium-severity vulnerability in n/a, published on 7 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in Object First Ootbi BETA build 1.0.7.712. A flaw was found in the Web Service, which could lead to local information disclosure. The command that creates the URL for the support bundle uses an insecure RNG. That can lead to prediction of the generated URL. As a result, an attacker can get access to system logs. An attacker would need credentials to exploit this vulnerability. This is fixed in Object First Ootbi BETA build 1.0.13.1611. Important note - This vulnerability is related to the Object First Ootbi BETA version, which is not released for production and therefore has no impact on the production environment. The production-ready Object First Ootbi version will have this vulnerability fixed.

Weakness: CWE-330 (Use of Insufficiently Random Values)

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

It affects 1 product.


Products: Objectfirst Ootbi.

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

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

## Is CVE-2022-44795 being exploited?

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

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-44795 is a medium-severity vulnerability in n/a, published on 7 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-44795 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-44795/ (Markdown: https://insights.sbomify.com/CVE-2022-44795/index.md)
```

## Sources

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

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