dbcve.org
Metasys Application And Data ServerApplication · Johnsoncontrols

CVE-2022-21937

MEDIUM · 5.4 CVSS v3.1 Published 2022-06-15
Fix available
A fix is available. Upgrade to 10.1.5 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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, a vulnerability in Metasys ADS/ADX/OAS 10 versions prior to 10.1.5 and Metasys ADS/ADX/OAS 11 versions prior to 11.0.2 could allow a user to inject malicious code into the web interface.

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

This is a cross-site scripting (XSS) vulnerability in the Metasys ADS/ADX/OAS building management system web interface. Under certain circumstances, an authenticated user could inject malicious client-side code that would execute in the browsers of other users viewing the affected interface.

MitigationUpgrade Metasys ADS/ADX/OAS to version 10.1.5 or later for the 10.x branch, or version 11.0.2 or later for the 11.x branch.

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.1
Metasys Extended Application And Data ServerApplication
Affected:>= 10.0, <= 10.1.5= 11.0= 11.0.1
Metasys Open Application ServerApplication
Affected:>= 10.0, < 10.1.5= 11.0= 11.0.1

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 component
    Determine whether the installed system is Metasys Application and Data Server (ADS), Extended Application and Data Server (ADX), or Open Application Server (OAS). Check system documentation, installed software list, or the application's login page for the component name.
    Affected if The component is ADS, ADX, or OAS from the affected product list.
  2. Check installed version
    Locate the installed version number of the Metasys component. This is typically accessible through the system administration console, the application's about page, or the installer information. Compare the version against the affected ranges: 10.0 through 10.1.5, 11.0, or 11.0.1.
    Affected if The installed version falls within 10.0 to 10.1.5 inclusive, or equals 11.0 or 11.0.1.
  3. Confirm web interface is enabled
    Verify that the Metasys web interface is accessible and enabled. This can be confirmed by attempting to access the web portal URL or checking the service configuration for web serving components.
    Affected if The web interface is accessible and no compensating controls block external access.
  4. Verify authentication configuration
    Check whether user authentication is configured and active for the Metasys web interface. The vulnerability requires an authenticated user to inject malicious code, so confirm that user accounts and authentication are enabled.
    Affected if Authentication is enabled and users can log in to the web interface.

A system is affected if it runs Metasys ADS, ADX, or OAS version 10.0 through 10.1.5, or version 11.0 or 11.0.1, with the web interface accessible and authentication enabled.

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 or later
Fixed in 10.1.5
Interim mitigation

Upgrade Metasys ADS/ADX/OAS to version 10.1.5 or later for the 10.x branch, or version 11.0.2 or later for the 11.x branch.

Recommended fix High confidence

Metasys 10.x: upgrade to 10.1.5 or later; Metasys 11.x: upgrade to 11.0.2 or later

  1. 1. Identify the currently installed Metasys version (ADS, ADX, or OAS) from the system console or administration interface
  2. 2. For Metasys 10.x versions (10.0 through 10.1.4.x): Upgrade to version 10.1.5 or later
  3. 3. For Metasys 11.x versions (11.0, 11.0.1): Upgrade to version 11.0.2 or later
  4. 4. After upgrade, verify the web interface loads correctly and test that the XSS vulnerability is remediated
  5. 5. Review Johnson Controls technical documentation for any specific upgrade prerequisites or procedures
Caveat Review release notes for any configuration or compatibility changes between versions; standard patching recommended during maintenance window

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
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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