{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-36802 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-36802 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-36802 is a medium-severity server-side request forgery vulnerability in Atlassian Jira Align, published on 14 Oct 2022. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-36802 and fix it if it is affected.\n\nWhat it is: CVE-2022-36802 is a medium-severity server-side request forgery vulnerability in Atlassian Jira Align, published on 14 Oct 2022. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-36802 in the wild and no public exploit code.\n\nAffected product: Atlassian Jira Align. 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-36802/ (Markdown: https://insights.sbomify.com/CVE-2022-36802/index.md)","id":"CVE-2022-36802","markdown":"https://insights.sbomify.com/CVE-2022-36802/index.md","name":"CVE-2022-36802","record":{"aliases":["GHSA-r626-8pv5-vwq9"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Jira Align","requires_auth":"high_privilege","summary":"Remote attackers with Super Admin privileges can exploit SSRF in Jira Align to access internal network resources.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"atlassian","cpe":[{"product":"jira_align","vendor":"atlassian"}],"cvss":{"score":4.9,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"The ManageJiraConnectors API in Atlassian Jira Align before version 10.109.2 allows remote attackers to exploit this issue to access internal network resources via a Server-Side Request Forgery. This can be exploited by a remote, unauthenticated attacker with Super Admin privileges by sending a specially crafted HTTP request.","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":"Server-side request forgery in Jira Align","id":"CVE-2022-36802","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege escalation in Jira Align","id":"CVE-2022-36803"},"packages":[],"prev":{"headline":"Cross-site scripting in Jira Data Center","id":"CVE-2022-36801"},"products":["Jira Align"],"published":"2022-10-14","related":[{"cvss_score":8.8,"headline":"Privilege escalation in Jira Align","id":"CVE-2022-36803","kev_date_added":null,"published":"2022-10-14"},{"cvss_score":5.3,"headline":"Missing authorization in Jira Align","id":"CVE-2025-22168","kev_date_added":null,"published":"2025-10-22"},{"cvss_score":5.3,"headline":"Missing authorization in Jira Align","id":"CVE-2025-22169","kev_date_added":null,"published":"2025-10-22"},{"cvss_score":5.3,"headline":"Missing authorization in Jira Align","id":"CVE-2025-22170","kev_date_added":null,"published":"2025-10-22"},{"cvss_score":5.3,"headline":"Missing authorization in Jira Align","id":"CVE-2025-22171","kev_date_added":null,"published":"2025-10-22"},{"cvss_score":5.3,"headline":"Missing authorization in Jira Align","id":"CVE-2025-22172","kev_date_added":null,"published":"2025-10-22"},{"cvss_score":5.3,"headline":"Missing authorization in Jira Align","id":"CVE-2025-22173","kev_date_added":null,"published":"2025-10-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":"partial"},"state":"PUBLISHED","updated":"2024-10-29","vendors":["Atlassian"]},"summary":"Remote attackers with Super Admin privileges can exploit SSRF in Jira Align to access internal network resources.","url":"https://insights.sbomify.com/CVE-2022-36802/"}