# CVE-2021-36206: CEVAS


- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2022
- **Updated:** 5 May 2025
- **Also known as:** GHSA-x6w6-px77-g4xh

## What is CVE-2021-36206?

CVE-2021-36206 is a critical vulnerability in Johnson Controls CEVAS, published on 28 Oct 2022. 

### Official description

All versions of CEVAS prior to 1.01.46 do not sufficiently validate user-controllable input and could allow a user to bypass authentication and retrieve data with specially crafted SQL queries.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Johnsoncontrols Cevas.

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

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

## Is CVE-2021-36206 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-36206 is a critical vulnerability in Johnson Controls CEVAS, published on 28 Oct 2022. 
Exploitation: There is no known exploitation of CVE-2021-36206 in the wild and no public exploit code.

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

## Sources

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

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