# CVE-2022-21936: Metasys MVE

> An Active Directory user can execute validated actions without a valid password in the Metasys MVE SMP UI, bypassing authentication controls.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Oct 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-jhww-39jr-3qqf

## What is CVE-2022-21936?

CVE-2022-21936 is a high-severity authentication bypass vulnerability in n/a, published on 7 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

On Metasys ADX Server version 12.0 running MVE, an Active Directory user could execute validated actions without providing a valid password when using MVE SMP UI.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Johnsoncontrols Metasys Extended Application and Data Server.

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

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

## Is CVE-2022-21936 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-21936 is a high-severity authentication bypass vulnerability in n/a, published on 7 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-21936 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-21936/ (Markdown: https://insights.sbomify.com/CVE-2022-21936/index.md)
```

## Sources

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

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