dbcve.org
Metasys System Configuration ToolApplication · Johnsoncontrols

CVE-2022-21940

MEDIUM · 6.1 CVSS v3.1 Published 2023-02-09
Fix available
A fix is available. Upgrade to 14.2.3 / 15.0.3 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Sensitive Cookie in HTTPS Session Without 'Secure' Attribute vulnerability in Johnson Controls System Configuration Tool (SCT) version 14 prior to 14.2.3 and version 15 prior to 15.0.3 could allow access to the cookie.

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

Johnson Controls System Configuration Tool (SCT) versions prior to 14.2.3 and 15.0.3 transmit sensitive cookies without the 'Secure' attribute, meaning cookies can be sent over unencrypted HTTP connections and potentially intercepted or leaked through mixed-content scenarios.

MitigationUpgrade SCT to version 14.2.3 or 15.0.3 (or later) to include the Secure flag on cookies, ensuring they are only transmitted over HTTPS connections.

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 System Configuration ToolApplication
Affected:>= 14.0, < 14.2.3>= 15.0, < 15.0.3

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Locate the installed SCT version
    Open the application, then navigate to Help > About, or check Add/Remove Programs (Windows) for Johnson Controls Metasys System Configuration Tool to find the installed version number
    Affected if The version shown is 14.0.x, 14.1.x, 14.2.0-14.2.2, 15.0.x, 15.0.1, or 15.0.2 (falls within >=14.0,<14.2.3 or >=15.0,<15.0.3)
  2. Compare against affected version ranges
    Check if your installed version is 14.0 through 14.2.2 (inclusive), or 15.0 through 15.0.2 (inclusive)
    Affected if Your version is 14.0 <= version < 14.2.3 OR 15.0 <= version < 15.0.3
  3. Confirm vulnerability via cookie inspection
    If the application exposes a web interface or API, use browser developer tools or a network proxy (like Fiddler) to capture HTTP responses and inspect Set-Cookie headers when authenticating or using the tool
    Affected if Any Set-Cookie header is missing the Secure attribute (no "; Secure" suffix) and the cookie appears sensitive (session tokens, authentication credentials)
  4. Check for HTTP traffic
    While running SCT, use a network monitoring tool to observe whether any HTTP (not HTTPS) requests are made that include cookies
    Affected if Cookies are transmitted over plain HTTP connections, confirming the missing Secure flag allows unencrypted transmission

You are affected if your installed SCT version is 14.0.0 through 14.2.2 or 15.0.0 through 15.0.2, and sensitive cookies are being set without the Secure attribute.

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 14.2.3 / 15.0.3 or later
Fixed in 14.2.315.0.3
Interim mitigation

Upgrade SCT to version 14.2.3 or 15.0.3 (or later) to include the Secure flag on cookies, ensuring they are only transmitted over HTTPS connections.

Recommended fix High confidence

Metasys SCT version 14.2.3 or 15.0.3 (depending on your current major version branch)

  1. 1. Identify the currently installed Metasys System Configuration Tool version via Help > About or system information
  2. 2. Backup the current SCT configuration and any related data
  3. 3. Download the appropriate fixed version from the official Johnson Controls website (14.2.3 for version 14.x or 15.0.3 for version 15.x)
  4. 4. Close any running instances of the System Configuration Tool
  5. 5. Run the installer for the fixed version
  6. 6. Follow the installation wizard prompts to complete the upgrade
  7. 7. After installation, verify the upgrade was successful by checking the version number
  8. 8. Test that cookies are now properly handled with the 'Secure' attribute in HTTPS sessions
Caveat No breaking changes documented in the provided materials

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

Fix this in Metasys System Configuration Tool Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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