{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-20401 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-20401 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-20401 is a medium-severity vulnerability in Atlassian Jira Server, published on 6 Feb 2020. 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-2019-20401 and fix it if it is affected.\n\nWhat it is: CVE-2019-20401 is a medium-severity vulnerability in Atlassian Jira Server, published on 6 Feb 2020. 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-2019-20401 in the wild and no public exploit code.\n\nAffected product: Atlassian Jira Server. 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-2019-20401/ (Markdown: https://insights.sbomify.com/CVE-2019-20401/index.md)","id":"CVE-2019-20401","markdown":"https://insights.sbomify.com/CVE-2019-20401/index.md","name":"CVE-2019-20401","record":{"aliases":["GHSA-9pj6-pcqj-h4qx"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Jira Server","requires_auth":"none","summary":"Attackers can exploit CSRF to configure a Jira instance during initial setup, bypassing security controls if the installation is incomplete.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"atlassian","cpe":[{"product":"jira_server","vendor":"atlassian"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Various installation setup resources in Jira before version 8.5.2 allow remote attackers to configure a Jira instance, which has not yet finished being installed, via Cross-site request forgery (CSRF) vulnerabilities.","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 Server","id":"CVE-2019-20401","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"atlassian:jira_server","products":["atlassian:jira_server"],"type":"csrf","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in Jira Server","id":"CVE-2019-20402"},"packages":[],"prev":{"headline":"Code injection in Jira Server","id":"CVE-2019-20400"},"products":["Jira Server"],"published":"2020-02-06","related":[{"cvss_score":9.8,"headline":"Atlassian Jira Server and Data Center Server-Side Template Injection","id":"CVE-2019-11581","kev_date_added":"2022-03-07","published":"2019-08-09"},{"cvss_score":7.8,"headline":"Code injection in Jira Server","id":"CVE-2019-20400","kev_date_added":null,"published":"2020-02-06"},{"cvss_score":6.5,"headline":"Denial of service in Jira Server","id":"CVE-2020-14177","kev_date_added":null,"published":"2020-09-21"},{"cvss_score":6.5,"headline":"Cross-site request forgery in Jira","id":"CVE-2019-14998","kev_date_added":null,"published":"2019-09-11"},{"cvss_score":6.5,"headline":"Server-side request forgery in Jira","id":"CVE-2019-8451","kev_date_added":null,"published":"2019-09-11"},{"cvss_score":6.1,"headline":"Cross-site scripting in Jira Data Center","id":"CVE-2021-43942","kev_date_added":null,"published":"2022-01-04"}],"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":["Atlassian"]},"summary":"Attackers can exploit CSRF to configure a Jira instance during initial setup, bypassing security controls if the installation is incomplete.","url":"https://insights.sbomify.com/CVE-2019-20401/"}