{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-21940 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-21940 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-21940 is a high-severity vulnerability in Johnson Controls System Configuration Tool (SCT), published on 9 Feb 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-21940 and fix it if it is affected.\n\nWhat it is: CVE-2022-21940 is a high-severity vulnerability in Johnson Controls System Configuration Tool (SCT), published on 9 Feb 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-21940 in the wild and no public exploit code.\n\nAffected product: Johnson Controls System Configuration Tool (SCT). No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-21940/ (Markdown: https://insights.sbomify.com/CVE-2022-21940/index.md)","id":"CVE-2022-21940","markdown":"https://insights.sbomify.com/CVE-2022-21940/index.md","name":"CVE-2022-21940","record":{"aliases":["GHSA-hp26-q6wq-vrfp"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"System Configuration Tool","requires_auth":"none","summary":"Attackers can access sensitive cookies from HTTPS sessions due to missing Secure attributes, potentially compromising user sessions in Johnson Controls SCT.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jci","cpe":[{"product":"metasys_system_configuration_tool","vendor":"johnsoncontrols"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-311","name":"Missing Encryption of Sensitive Data"},{"id":"CWE-614","name":"Sensitive Cookie in HTTPS Session Without 'Secure' Attribute"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Sensitive Cookie in HTTPS Session Without 'Secure' Attribute in System Configuration Tool (SCT)","id":"CVE-2022-21940","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"iSTAR Ultra","id":"CVE-2022-21941"},"packages":[],"prev":{"headline":"Sensitive cookie without 'HttpOnly' flag in System Configuration Tool (SCT)","id":"CVE-2022-21939"},"products":["System Configuration Tool (SCT)"],"published":"2023-02-09","related":[{"cvss_score":7.5,"headline":"Sensitive cookie without 'HttpOnly' flag in System Configuration Tool (SCT)","id":"CVE-2022-21939","kev_date_added":null,"published":"2023-02-09"},{"cvss_score":5.3,"headline":"Johnson Controls Metasys SCT Pro","id":"CVE-2021-36203","kev_date_added":null,"published":"2022-04-22"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-03-24","vendors":["Johnson Controls"]},"summary":"Attackers can access sensitive cookies from HTTPS sessions due to missing Secure attributes, potentially compromising user sessions in Johnson Controls SCT.","url":"https://insights.sbomify.com/CVE-2022-21940/"}