# CVE-2022-24328: Denial of service in n/a

> An unprivileged user can cause a denial of service in JetBrains Hub, requiring an upgrade to mitigate.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:** 25 Feb 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-hh4r-8h4c-83j4

## What is CVE-2022-24328?

CVE-2022-24328 is a medium-severity denial of service vulnerability in n/a, published on 25 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In JetBrains Hub before 2021.1.13956, an unprivileged user could perform DoS.

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

It affects 1 product.


Products: Jetbrains Hub.

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

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

## Is CVE-2022-24328 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-50242](https://insights.sbomify.com/CVE-2026-50242/): Auth bypass in Hub (critical 10.0)
- [CVE-2026-56141](https://insights.sbomify.com/CVE-2026-56141/): Weak cryptography in Hub (critical 9.8)
- [CVE-2022-25262](https://insights.sbomify.com/CVE-2022-25262/): Auth bypass in n/a (critical 9.8)
- [CVE-2021-43183](https://insights.sbomify.com/CVE-2021-43183/): Security feature bypass in n/a (critical 9.8)
- [CVE-2021-36209](https://insights.sbomify.com/CVE-2021-36209/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-24328 is a medium-severity denial of service vulnerability in n/a, published on 25 Feb 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-24328 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-24328/ (Markdown: https://insights.sbomify.com/CVE-2022-24328/index.md)
```

## Sources

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

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