dbcve.org
Metasys Application And Data ServerApplication · Johnsoncontrols

CVE-2021-36207

HIGH · 8.8 CVSS v3.1 Published 2022-04-29
Fix available
A fix is available. Upgrade to 10.1.5 / 11.0.2 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Under certain circumstances improper privilege management in Metasys ADS/ADX/OAS servers versions 10 and 11 could allow an authenticated user to elevate their privileges to administrator.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a privilege escalation vulnerability in Metasys ADS/ADX/OAS servers versions 10 and 11 where improper privilege management allows an authenticated user to elevate their privileges to administrator level under certain circumstances.

MitigationApply vendor patches or updates for Metasys versions 10 and 11, and review user privilege assignments to ensure least-privilege principles are enforced until the patch is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Metasys Application And Data ServerApplication
Affected:>= 10.0, < 10.1.5>= 11.0, < 11.0.2
Metasys Extended Application And Data ServerApplication
Affected:>= 10.0, < 10.1.5>= 11.0, < 11.0.2
Metasys Open Application ServerApplication
Affected:>= 10.0, < 10.1.5>= 11.0, < 11.0.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Metasys product
    Locate the Metasys server installation and check the product name (Application And Data Server, Extended Application And Data Server, or Open Application Server). This is typically visible in the Metasys system information or installed programs list.
    Affected if The product is one of ADS, ADX, or OAS.
  2. Determine the installed version number
    Access the Metasys system information or version details panel to find the exact installed version (for example, 10.1.3 or 11.0.1). Consult the Metasys documentation for the specific location of version information in your deployment.
    Affected if The version is 10.0.x through 10.1.4, or 11.0.x through 11.0.1.
  3. Compare against affected version ranges
    Using the version identified in step 2, verify whether it falls within the affected ranges: 10.0.0 to 10.1.4 (inclusive) or 11.0.0 to 11.0.1 (inclusive). Versions 10.1.5 and above, or 11.0.2 and above, are not affected.
    Affected if The installed version is less than 10.1.5 (for 10.x releases) or less than 11.0.2 (for 11.x releases).
  4. Verify presence of authenticated non-administrator users
    Review the Metasys user database or directory to confirm whether there are authenticated users with standard or limited privileges configured in the system. Check user role assignments through the Metasys administration interface.
    Affected if Non-administrator user accounts exist in the system who could potentially exploit the privilege escalation flaw.

A user is affected if the Metasys ADS, ADX, or OAS server is running version 10.0.x through 10.1.4 or version 11.0.x through 11.0.1 and has non-administrator user accounts present.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.1.5 / 11.0.2 or later
Fixed in 10.1.511.0.2
Interim mitigation

Apply vendor patches or updates for Metasys versions 10 and 11, and review user privilege assignments to ensure least-privilege principles are enforced until the patch is applied.

Recommended fix High confidence

Upgrade to 10.1.5 for v10.x line, or 11.0.2 for v11.x line

  1. Backup the Metasys server configuration and database before initiating any upgrade
  2. Review Johnson Controls release notes for version 10.1.5 (for 10.x installations) or 11.0.2 (for 11.x installations) to understand changes
  3. Ensure all prerequisites for the upgrade are met per Johnson Controls documentation
  4. Upgrade Metasys ADS/ADX/OAS servers from versions 10.0-10.1.4 to version 10.1.5
  5. Upgrade Metasys ADS/ADX/OAS servers from versions 11.0-11.0.1 to version 11.0.2
  6. Verify the upgrade was successful by confirming server functionality
  7. Test that privilege elevation no longer occurs for authenticated non-admin users
Caveat Point release upgrades typically have minimal breaking changes; review release notes for any configuration or integration changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Metasys Application And Data Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,780
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-36207 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-36207 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data