{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-36800 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-36800 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-36800 is a medium-severity vulnerability in Atlassian Jira Service Management Data Center, published on 3 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-36800 and fix it if it is affected.\n\nWhat it is: CVE-2022-36800 is a medium-severity vulnerability in Atlassian Jira Service Management Data Center, published on 3 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-36800 in the wild and no public exploit code.\n\nAffected product: Atlassian Jira Service Management Data Center. 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-36800/ (Markdown: https://insights.sbomify.com/CVE-2022-36800/index.md)","id":"CVE-2022-36800","markdown":"https://insights.sbomify.com/CVE-2022-36800/index.md","name":"CVE-2022-36800","record":{"aliases":["GHSA-mx26-3rqj-88q7"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jira Service Management","requires_auth":"low_privilege","summary":"Remote attackers without Browse Users permission can view group information via an information disclosure flaw in Jira Service Management.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"atlassian","cpe":[{"product":"jira_service_management","vendor":"atlassian"}],"cvss":{"score":4.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"Affected versions of Atlassian Jira Service Management Server and Data Center allow remote attackers without the \"Browse Users\" permission to view groups via an Information Disclosure vulnerability in the browsegroups.action endpoint. The affected versions are before version 4.22.2.","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":"Information disclosure in Jira Service Management Data Center","id":"CVE-2022-36800","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in Jira Data Center","id":"CVE-2022-36801"},"packages":[],"prev":{"headline":"Code injection in Jira Data Center","id":"CVE-2022-36799"},"products":["Jira Service Management Data Center","Jira Service Management Server"],"published":"2022-08-03","related":[{"cvss_score":9.4,"headline":"Auth bypass in Jira Service Management Data Center","id":"CVE-2023-22501","kev_date_added":null,"published":"2023-02-01"},{"cvss_score":4.8,"headline":"Cross-site scripting in Jira Service Management Data Center","id":"CVE-2021-43943","kev_date_added":null,"published":"2022-02-24"},{"cvss_score":4.3,"headline":"Missing authorization in Jira Service Management Data Center","id":"CVE-2021-43948","kev_date_added":null,"published":"2022-02-15"},{"cvss_score":4.3,"headline":"Missing authorization in Jira Service Management Data Center","id":"CVE-2021-43950","kev_date_added":null,"published":"2022-02-15"},{"cvss_score":4.3,"headline":"Missing authorization in Jira Service Management Data Center","id":"CVE-2021-43949","kev_date_added":null,"published":"2022-01-10"},{"cvss_score":4.3,"headline":"Information disclosure in Jira Service Management Data Center","id":"CVE-2021-43951","kev_date_added":null,"published":"2022-01-10"}],"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":"partial"},"state":"PUBLISHED","updated":"2024-10-29","vendors":["Atlassian"]},"summary":"Remote attackers without Browse Users permission can view group information via an information disclosure flaw in Jira Service Management.","url":"https://insights.sbomify.com/CVE-2022-36800/"}