# CVE-2022-3423: Allocation of Resources Without Limits or Throttling in nocodb/nocodb

> Attackers can cause denial of service in NocoDB by exploiting resource allocation limits, requiring an upgrade to mitigate.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 7 Oct 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-grv6-m753-3w2g

## What is CVE-2022-3423?

CVE-2022-3423 is a high-severity denial of service vulnerability in nocodb/nocodb, published on 7 Oct 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Allocation of Resources Without Limits or Throttling in GitHub repository nocodb/nocodb prior to 0.92.0.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

2 open source packages ship an affected version, including nocodb. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nocodb` | npm | All versions | 0.92.0 |
| `nocodb` | npm | All versions | 0.92.0 |

Products: Nocodb Nocodb.

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

Upgrade nocodb to 0.92.0 or later.

## Is CVE-2022-3423 being exploited?

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

## Other vulnerabilities in nocodb/nocodb

- [CVE-2022-2339](https://insights.sbomify.com/CVE-2022-2339/): Server-Side Request Forgery (SSRF) in nocodb/nocodb (critical 9.1)
- [CVE-2022-2062](https://insights.sbomify.com/CVE-2022-2062/): Generation of Error Message Containing Sensitive Information in nocodb/nocodb (critical 9.1)
- [CVE-2022-2064](https://insights.sbomify.com/CVE-2022-2064/): Insufficient Session Expiration in nocodb/nocodb (critical 9.1)
- [CVE-2022-2063](https://insights.sbomify.com/CVE-2022-2063/): Improper Privilege Management in nocodb/nocodb (critical 9.0)
- [CVE-2022-2022](https://insights.sbomify.com/CVE-2022-2022/): Cross-site Scripting (XSS) - Stored in nocodb/nocodb (critical 9.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-3423 is a high-severity denial of service vulnerability in nocodb/nocodb, published on 7 Oct 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-3423 in the wild and no public exploit code.

Affected packages and fixed versions:
- nocodb (npm): affected all versions; fixed in 0.92.0
- nocodb (npm): affected all versions; fixed in 0.92.0

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-3423/ (Markdown: https://insights.sbomify.com/CVE-2022-3423/index.md)
```

## Sources

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

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