dbcve.org
Metasys Application And Data ServerApplication · Johnsoncontrols

CVE-2021-36200

MEDIUM · 5.3 CVSS v3.1 Published 2022-07-22
Fix available
A fix is available. Upgrade to 10.1.6 / 11.0.2 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 an unauthenticated user could access the the web API for Metasys ADS/ADX/OAS 10 versions prior to 10.1.6 and 11 versions prior to 11.0.2 and enumerate users.

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 · high confidence

An information disclosure vulnerability in Metasys ADS/ADX/OAS web API versions prior to 10.1.6 and 11.0.2 allows unauthenticated attackers to enumerate valid user accounts through the web API endpoint.

MitigationUpgrade Metasys ADS/ADX/OAS to version 10.1.6 or 11.0.2 or later to patch the user enumeration vulnerability in the web API.

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.6>= 11.0, < 11.0.2
Metasys Extended Application And Data ServerApplication
Affected:>= 10.0, < 10.1.6>= 11.0, < 11.0.2
Metasys Open Application ServerApplication
Affected:>= 10.0, < 10.1.6>= 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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

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 Metasys product and version
    Access the Metasys web interface or system information page (typically through the About or System Info section in the administration console) and record the exact version number of the ADS, ADX, or OAS installation.
    Affected if The installed version is prior to 10.1.6 for version 10.x releases, or prior to 11.0.2 for version 11.x releases.
  2. Confirm web API is accessible
    Attempt to access the Metasys web API endpoint (typically at /api or /MetasysAPI on the server's web interface) from an unauthenticated network perspective to determine if the API is exposed.
    Affected if The web API endpoint is reachable without authentication from the network.
  3. Test for user enumeration via API
    Send unauthenticated HTTP requests to the web API login or user endpoint with different potential usernames and analyze the response differences (such as response codes, error messages, or timing) to see if the API reveals which accounts are valid.
    Affected if The API returns distinct responses that allow differentiation between valid and invalid user accounts (e.g., different error messages for valid vs invalid usernames).

A defender is affected if the Metasys ADS/ADX/OAS version is 10.0 to <10.1.6 or 11.0 to <11.0.2 AND the web API is accessible to unauthenticated attackers who can enumerate valid user accounts.

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.6 / 11.0.2 or later
Fixed in 10.1.611.0.2
Interim mitigation

Upgrade Metasys ADS/ADX/OAS to version 10.1.6 or 11.0.2 or later to patch the user enumeration vulnerability in the web API.

Recommended fix High confidence

Metasys ADS/ADX/OAS 10.1.6 or later (for v10.x); Metasys ADS/ADX/OAS 11.0.2 or later (for v11.x)

  1. 1. Identify the current version of Metasys ADS/ADX/OAS installation by checking the system information or version logs.
  2. 2. For Metasys v10.x installations: Plan an upgrade to version 10.1.6 or later.
  3. 3. For Metasys v11.x installations: Plan an upgrade to version 11.0.2 or later.
  4. 4. Before upgrading, review release notes and upgrade documentation from Johnson Controls for any specific upgrade requirements or prerequisites.
  5. 5. Perform a backup of the current system configuration and data.
  6. 6. Test the upgrade in a non-production environment first.
  7. 7. Apply the upgrade following Johnson Controls official upgrade procedures.
  8. 8. After upgrade, verify that the web API now properly requires authentication and user enumeration is no longer possible.
Caveat Standard minor version upgrade - review release notes for any configuration or compatibility 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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-36200 — 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-36200 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