{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2021-36205 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-36205 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-36205 is a high-severity vulnerability in Johnson Controls Metasys, published on 15 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-36205 and fix it if it is affected.\n\nWhat it is: CVE-2021-36205 is a high-severity vulnerability in Johnson Controls Metasys, published on 15 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-36205 in the wild and no public exploit code.\n\nAffected product: Johnson Controls Metasys. 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-2021-36205/ (Markdown: https://insights.sbomify.com/CVE-2021-36205/index.md)","id":"CVE-2021-36205","markdown":"https://insights.sbomify.com/CVE-2021-36205/index.md","name":"CVE-2021-36205","record":{"aliases":["GHSA-rcgx-6rcq-v2mx"],"analysis":{"component_type":"ics_ot","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Building automation system","requires_auth":"none","summary":"Attackers can maintain unauthorized access after logout because session tokens are not cleared, affecting Johnson Controls Metasys users.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jci","cpe":[{"product":"metasys_application_and_data_server","vendor":"johnsoncontrols"},{"product":"metasys_extended_application_and_data_server","vendor":"johnsoncontrols"},{"product":"metasys_open_application_server","vendor":"johnsoncontrols"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-459","name":"Incomplete Cleanup"}],"description":"Under certain circumstances the session token is not cleared on logout.","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":"Metasys session token","id":"CVE-2021-36205","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"CEVAS","id":"CVE-2021-36206"},"packages":[],"prev":{"headline":"Insufficiently Protected Credentials in Metasys","id":"CVE-2021-36204"},"products":["Metasys"],"published":"2022-04-15","related":[{"cvss_score":8.8,"headline":"Metasys privilege management","id":"CVE-2021-36207","kev_date_added":null,"published":"2022-04-29"},{"cvss_score":8.7,"headline":"Metasys CSS","id":"CVE-2022-21937","kev_date_added":null,"published":"2022-06-15"},{"cvss_score":8.4,"headline":"Metasys UI","id":"CVE-2021-36202","kev_date_added":null,"published":"2022-04-07"},{"cvss_score":8.1,"headline":"Metasys MUI Graphics XSS","id":"CVE-2022-21938","kev_date_added":null,"published":"2022-06-15"},{"cvss_score":8,"headline":"Metasys Unverified Password Change","id":"CVE-2022-21934","kev_date_added":null,"published":"2022-05-06"},{"cvss_score":7.8,"headline":"Insufficiently Protected Credentials in Metasys","id":"CVE-2021-36204","kev_date_added":null,"published":"2023-01-13"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["Johnson Controls"]},"summary":"Attackers can maintain unauthorized access after logout because session tokens are not cleared, affecting Johnson Controls Metasys users.","url":"https://insights.sbomify.com/CVE-2021-36205/"}