{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-20400 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-20400 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-20400 is a high-severity code injection vulnerability in Atlassian Jira Server, published on 6 Feb 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-20400 and fix it if it is affected.\n\nWhat it is: CVE-2019-20400 is a high-severity code injection vulnerability in Atlassian Jira Server, published on 6 Feb 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-20400 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-20400/ (Markdown: https://insights.sbomify.com/CVE-2019-20400/index.md)","id":"CVE-2019-20400","markdown":"https://insights.sbomify.com/CVE-2019-20400/index.md","name":"CVE-2019-20400","record":{"aliases":["GHSA-j87m-3c97-hhhg"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Jira Server","requires_auth":"none","summary":"Local attackers can execute arbitrary code via DLL hijacking in Jira Server by writing to a directory in the global path environment variable.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"atlassian","cpe":[{"product":"jira_server","vendor":"atlassian"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-427","name":"Uncontrolled Search Path Element"}],"description":"The usage of Tomcat in Jira before version 8.5.2 allows local attackers with permission to write a dll file to a directory in the global path environmental variable can inject code into via a DLL hijacking vulnerability.","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":"Code injection in Jira Server","id":"CVE-2019-20400","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"atlassian:jira_server","products":["atlassian:jira_server"],"type":"code_injection","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site request forgery in Jira Server","id":"CVE-2019-20401"},"packages":[],"prev":{"headline":"Observable Discrepancy in libsecp256k1-rs","id":"CVE-2019-20399"},"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":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 Server","id":"CVE-2019-20401","kev_date_added":null,"published":"2020-02-06"},{"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":"Local attackers can execute arbitrary code via DLL hijacking in Jira Server by writing to a directory in the global path environment variable.","url":"https://insights.sbomify.com/CVE-2019-20400/"}