{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2021-43953 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-43953 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-43953 is a medium-severity vulnerability in Atlassian Jira, published on 15 Feb 2022. 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-2021-43953 and fix it if it is affected.\n\nWhat it is: CVE-2021-43953 is a medium-severity vulnerability in Atlassian Jira, published on 15 Feb 2022. 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-2021-43953 in the wild and no public exploit code.\n\nAffected product: Atlassian Jira. 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-43953/ (Markdown: https://insights.sbomify.com/CVE-2021-43953/index.md)","id":"CVE-2021-43953","markdown":"https://insights.sbomify.com/CVE-2021-43953/index.md","name":"CVE-2021-43953","record":{"aliases":["GHSA-j485-xjwc-7p25"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Jira Server","requires_auth":"none","summary":"Unauthenticated attackers can toggle monitoring settings via CSRF, requiring administrators to upgrade Jira Server or Data Center.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"atlassian","cpe":[{"product":"data_center","vendor":"atlassian"},{"product":"jira","vendor":"atlassian"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Affected versions of Atlassian Jira Server and Data Center allow unauthenticated remote attackers to toggle the Thread Contention and CPU monitoring settings via a Cross-Site Request Forgery (CSRF) vulnerability in the /secure/admin/ViewInstrumentation.jspa endpoint. The affected versions are before version 8.13.16, and from version 8.14.0 before 8.20.5.","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":"Cross-site request forgery in Jira Data Center","id":"CVE-2021-43953","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"atlassian:jira","products":["atlassian:jira"],"type":"csrf","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Server-side request forgery in Crucible","id":"CVE-2021-43954"},"packages":[],"prev":{"headline":"Affected versions of Atlassian Jira Server and Data Center allow unauthenticated remote attackers to restore the default configuration of fi","id":"CVE-2021-43952"},"products":["Jira Data Center","Jira Server"],"published":"2022-02-15","related":[{"cvss_score":8.8,"headline":"Code injection in Jira Data Center","id":"CVE-2017-18113","kev_date_added":null,"published":"2021-08-02"},{"cvss_score":7.5,"headline":"Auth bypass in Jira Data Center","id":"CVE-2021-41312","kev_date_added":null,"published":"2021-11-03"},{"cvss_score":7.5,"headline":"Denial of service in Jira Data Center","id":"CVE-2021-39123","kev_date_added":null,"published":"2021-09-14"},{"cvss_score":7.5,"headline":"Missing authorization in Jira Data Center","id":"CVE-2021-39113","kev_date_added":null,"published":"2021-08-30"},{"cvss_score":7.2,"headline":"Code injection in Jira Data Center","id":"CVE-2021-43947","kev_date_added":null,"published":"2022-01-06"},{"cvss_score":7.2,"headline":"Auth bypass in Jira Data Center","id":"CVE-2021-26070","kev_date_added":null,"published":"2021-03-22"},{"cvss_score":6.1,"headline":"Cross-site scripting in Jira Data Center","id":"CVE-2021-41304","kev_date_added":null,"published":"2021-10-26"}],"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-08","vendors":["Atlassian"]},"summary":"Unauthenticated attackers can toggle monitoring settings via CSRF, requiring administrators to upgrade Jira Server or Data Center.","url":"https://insights.sbomify.com/CVE-2021-43953/"}