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

> An issue in BigAnt Server allows attackers to cause a Denial of Service condition.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 21 Mar 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-2gg3-23vh-j2pg

## What is CVE-2022-23352?

CVE-2022-23352 is a high-severity denial of service vulnerability in n/a, published on 21 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in BigAnt Software BigAnt Server v5.6.06 can lead to a Denial of Service (DoS).

Weakness: CWE-835 (Loop with Unreachable Exit Condition)

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

It affects 1 product.


Products: Bigantsoft Bigant Server.

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

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

## Is CVE-2022-23352 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-0364](https://insights.sbomify.com/CVE-2025-0364/): BigAntSoft BigAnt Server Account Registration Bypass to File Upload RCE (critical 9.8)
- [CVE-2022-23346](https://insights.sbomify.com/CVE-2022-23346/): File upload in n/a (high 8.8)
- [CVE-2022-23349](https://insights.sbomify.com/CVE-2022-23349/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2022-26281](https://insights.sbomify.com/CVE-2022-26281/): Missing authorization in n/a (high 7.5)
- [CVE-2022-23345](https://insights.sbomify.com/CVE-2022-23345/): Missing authorization in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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