# CVE-2022-28936: Integer overflow in n/a

> A malicious node can cause a Denial of Service in FISCO-BCOS by sending an unusually large viewchange message packet that triggers an integer overflow.

- **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:** 15 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-6v7w-96vq-2xm3

## What is CVE-2022-28936?

CVE-2022-28936 is a high-severity vulnerability in n/a, published on 15 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FISCO-BCOS release-3.0.0-rc2 was discovered to contain an issue where a malicious node can trigger an integer overflow and cause a Denial of Service (DoS) via an unusually large viewchange message packet.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Fisco-Bcos Fisco-Bcos.

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

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

## Is CVE-2022-28936 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-28937](https://insights.sbomify.com/CVE-2022-28937/): Denial of service in n/a (high 7.5)
- [CVE-2022-26534](https://insights.sbomify.com/CVE-2022-26534/): Denial of service in n/a (high 7.5)
- [CVE-2021-46359](https://insights.sbomify.com/CVE-2021-46359/): Business logic in n/a (high 7.5)
- [CVE-2021-35041](https://insights.sbomify.com/CVE-2021-35041/): Denial of service in n/a (high 7.5)
- [CVE-2024-58131](https://insights.sbomify.com/CVE-2024-58131/): Race condition in FISCO-BCOS (medium 4.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-28936 is a high-severity vulnerability in n/a, published on 15 May 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-28936 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-28936/ (Markdown: https://insights.sbomify.com/CVE-2022-28936/index.md)
```

## Sources

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

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