{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2021-43959 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-43959 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-43959 is a medium-severity server-side request forgery vulnerability in Atlassian Jira Service Management Data Center, published on 26 Jul 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-43959 and fix it if it is affected.\n\nWhat it is: CVE-2021-43959 is a medium-severity server-side request forgery vulnerability in Atlassian Jira Service Management Data Center, published on 26 Jul 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2021-43959 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-2021-43959/ (Markdown: https://insights.sbomify.com/CVE-2021-43959/index.md)","id":"CVE-2021-43959","markdown":"https://insights.sbomify.com/CVE-2021-43959/index.md","name":"CVE-2021-43959","record":{"aliases":["GHSA-5rqp-fx48-4mvw"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Jira Service Management","requires_auth":"low_privilege","summary":"Authenticated attackers can exploit SSRF in CSV import to access internal network resources and cloud metadata credentials.","user_interaction":"required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"atlassian","cpe":[{"product":"jira_service_desk","vendor":"atlassian"},{"product":"jira_service_management","vendor":"atlassian"}],"cvss":{"score":5.7,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Affected versions of Atlassian Jira Service Management Server and Data Center allow authenticated remote attackers to access the content of internal network resources via a Server-Side Request Forgery (SSRF) vulnerability in the CSV importing feature of JSM Insight. When running in an environment like Amazon EC2, this flaw may be used to access to a metadata resource that provides access credentials and other potentially confidential information. The affected versions are before version 4.13.20, from version 4.14.0 before 4.20.8, and from version 4.21.0 before 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":"Server-side request forgery in Jira Service Management Data Center","id":"CVE-2021-43959","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2021-43960"},"packages":[],"prev":{"headline":"Security feature bypass in Crucible","id":"CVE-2021-43958"},"products":["Jira Service Management Data Center","Jira Service Management Server"],"published":"2022-07-26","related":[{"cvss_score":7.5,"headline":"Path traversal in Jira Service Desk Data Center","id":"CVE-2019-15004","kev_date_added":null,"published":"2019-11-07"},{"cvss_score":7.5,"headline":"Path traversal in Jira Service Desk Data Center","id":"CVE-2019-14994","kev_date_added":null,"published":"2019-09-19"},{"cvss_score":7.2,"headline":"Code injection in Jira Service Desk Data Center","id":"CVE-2021-39115","kev_date_added":null,"published":"2021-09-01"},{"cvss_score":5.3,"headline":"Missing authorization in Jira Service Desk Data Center","id":"CVE-2019-15003","kev_date_added":null,"published":"2019-11-07"},{"cvss_score":4.8,"headline":"Cross-site scripting in Jira Service Desk Server and Data Center","id":"CVE-2020-14166","kev_date_added":null,"published":"2020-07-01"},{"cvss_score":4.3,"headline":"Information disclosure in Jira Service Desk Server","id":"CVE-2020-14180","kev_date_added":null,"published":"2020-09-21"}],"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-03","vendors":["Atlassian"]},"summary":"Authenticated attackers can exploit SSRF in CSV import to access internal network resources and cloud metadata credentials.","url":"https://insights.sbomify.com/CVE-2021-43959/"}