{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-20419 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-20419 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-20419 is a high-severity vulnerability in Atlassian Jira Data Center, published on 3 Jul 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-20419 and fix it if it is affected.\n\nWhat it is: CVE-2019-20419 is a high-severity vulnerability in Atlassian Jira Data Center, published on 3 Jul 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-20419 in the wild and no public exploit code.\n\nAffected product: Atlassian Jira 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-2019-20419/ (Markdown: https://insights.sbomify.com/CVE-2019-20419/index.md)","id":"CVE-2019-20419","markdown":"https://insights.sbomify.com/CVE-2019-20419/index.md","name":"CVE-2019-20419","record":{"aliases":["GHSA-w82j-w856-p8j6"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Jira Server","requires_auth":"none","summary":"Remote attackers can execute arbitrary code via DLL hijacking in Tomcat within Atlassian Jira Server and Data Center.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"atlassian","cpe":[{"product":"jira_data_center","vendor":"atlassian"},{"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":"Affected versions of Atlassian Jira Server and Data Center allow remote attackers to execute arbitrary code via a DLL hijacking vulnerability in Tomcat. The affected versions are before version 8.5.5, and from version 8.6.0 before 8.7.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":"Other in Jira Server","id":"CVE-2019-20419","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"atlassian:jira_data_center","products":["atlassian:jira_data_center","atlassian:jira_server"],"type":"other","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in n/a","id":"CVE-2019-20421"},"packages":[],"prev":{"headline":"Denial of service in Jira Server","id":"CVE-2019-20418"},"products":["Jira Server"],"published":"2020-07-03","related":[{"cvss_score":5.3,"headline":"Atlassian Jira Server and Data Center Path Traversal","id":"CVE-2021-26086","kev_date_added":"2024-11-12","published":"2021-08-16"},{"cvss_score":9.8,"headline":"Auth bypass in Jira Core Server","id":"CVE-2022-0540","kev_date_added":null,"published":"2022-04-20"},{"cvss_score":9.8,"headline":"Deserialization in Jira Core Data Center","id":"CVE-2020-36239","kev_date_added":null,"published":"2021-07-29"},{"cvss_score":8.7,"headline":"Path traversal in Jira Software Data Center","id":"CVE-2025-22167","kev_date_added":null,"published":"2025-10-22"},{"cvss_score":7.4,"headline":"Information disclosure in Jira Core Data Center","id":"CVE-2024-21685","kev_date_added":null,"published":"2024-06-18"},{"cvss_score":7.2,"headline":"This High severity PrivEsc (Privilege Escalation) vulnerability was introduced in versions: 9.12.0, 10.3.0, 10.4.0, and 10.5.0 of Jira Core","id":"CVE-2025-22157","kev_date_added":null,"published":"2025-05-20"}],"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-17","vendors":["Atlassian"]},"summary":"Remote attackers can execute arbitrary code via DLL hijacking in Tomcat within Atlassian Jira Server and Data Center.","url":"https://insights.sbomify.com/CVE-2019-20419/"}