Skip to content
Fencer Intel
high 7.5

CVE-2022-21940 json

Sensitive Cookie in HTTPS Session Without 'Secure' Attribute in System Configuration Tool (SCT)

published 3y ago modified 4mo ago also EUVD-2022-27096

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 31%
public exploits
0
none known

Summary

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.

Patch / fix

  • Johnson Controls System Configuration Tool (SCT) 14.2.3, 15.0.3

Is CVE-2022-21940 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-23-040-03 updated cvss 7.5

Johnson Controls System Configuration Tool (SCT)

  • Johnson Controls System Configuration Tool (SCT) version 14 < 14.2.3 Johnson Controls System Configuration Tool (SCT) version 15 < 15.0.3
    affected: mitigation “Johnson Controls recommends users take the following actions to mitigate the vulnerabilities.” johnsoncontrols.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

0.37% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Affected products

  • Johnson Controls System Configuration Tool (SCT)

Classification

Weakness
  • CWE-614 Sensitive Cookie in HTTPS Session Without 'Secure' Attribute
  • CWE-311 Missing Encryption of Sensitive Data

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.