# CVE-2022-26779: Apache Cloudstack insecure random number generation affects project email invitation

> Attackers can brute force insecure project invitation tokens to hijack invites, requiring non-default configuration and existing user access.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 15 Mar 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-vpcc-9rh2-8jfp

## What is CVE-2022-26779?

CVE-2022-26779 is a high-severity vulnerability in Apache Cloudstack, published on 15 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Apache CloudStack prior to 4.16.1.0 used insecure random number generation for project invitation tokens. If a project invite is created based only on an email address, a random token is generated. An attacker with knowledge of the project ID and the fact that the invite is sent, could generate time deterministic tokens and brute force attempt to use them prior to the legitimate receiver accepting the invite. This feature is not enabled by default, the attacker is required to know or guess the project ID for the invite in addition to the invitation token, and the attacker would need to be an existing authorized user of CloudStack.

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

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

It affects 1 product.


Products: Apache Cloudstack.

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

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

## Is CVE-2022-26779 being exploited?

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

## Other vulnerabilities in Apache Cloudstack

- [CVE-2012-4501](https://insights.sbomify.com/CVE-2012-4501/): Missing authorization in n/a (critical 10.0)
- [CVE-2024-38346](https://insights.sbomify.com/CVE-2024-38346/): Apache CloudStack: Unauthenticated cluster service port leads to remote execution (critical 9.8)
- [CVE-2024-39864](https://insights.sbomify.com/CVE-2024-39864/): Apache CloudStack: Integration API service uses dynamic port when disabled (critical 9.8)
- [CVE-2024-29006](https://insights.sbomify.com/CVE-2024-29006/): Apache CloudStack: x-forwarded-for HTTP header parsed by default (critical 9.8)
- [CVE-2022-35741](https://insights.sbomify.com/CVE-2022-35741/): Apache CloudStack SAML Single Sign-On XXE (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-26779 is a high-severity vulnerability in Apache Cloudstack, published on 15 Mar 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-26779 in the wild and no public exploit code.

Affected product: Apache Cloudstack. 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-26779/ (Markdown: https://insights.sbomify.com/CVE-2022-26779/index.md)
```

## Sources

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

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