# CVE-2021-36199: VideoEdge

> Running a vulnerability scanner against VideoEdge NVRs can cause functionality to stop, leading to denial of service.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jan 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-g24j-p7x6-xgf7

## What is CVE-2021-36199?

CVE-2021-36199 is a medium-severity denial of service vulnerability in Johnson Controls VideoEdge, published on 14 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Running a vulnerability scanner against VideoEdge NVRs can cause some functionality to stop.

Weakness: CWE-228 (Improper Handling of Syntactically Invalid Structure)

## Which versions are affected by CVE-2021-36199?

It affects 1 product.


Products: Johnsoncontrols Videoedge.

## How do I fix CVE-2021-36199?

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

## Is CVE-2021-36199 being exploited?

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

## Other vulnerabilities in Johnson Controls VideoEdge

- [CVE-2023-3749](https://insights.sbomify.com/CVE-2023-3749/): VideoEdge config (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-36199 and fix it if it is affected.

What it is: CVE-2021-36199 is a medium-severity denial of service vulnerability in Johnson Controls VideoEdge, published on 14 Jan 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-2021-36199 in the wild and no public exploit code.

Affected product: Johnson Controls VideoEdge. 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-2021-36199/ (Markdown: https://insights.sbomify.com/CVE-2021-36199/index.md)
```

## Sources

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

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