{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-20898 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-20898 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-20898 is a high-severity vulnerability in Atlassian Jira, published on 13 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-20898 and fix it if it is affected.\n\nWhat it is: CVE-2019-20898 is a high-severity vulnerability in Atlassian Jira, published on 13 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-20898 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-2019-20898/ (Markdown: https://insights.sbomify.com/CVE-2019-20898/index.md)","id":"CVE-2019-20898","markdown":"https://insights.sbomify.com/CVE-2019-20898/index.md","name":"CVE-2019-20898","record":{"aliases":["GHSA-vm5f-v8rf-rwpx"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jira Server","requires_auth":"none","summary":"Remote attackers can access sensitive information in the Global permissions screen without authentication, requiring an upgrade to Jira Server.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"atlassian","cpe":[{"product":"jira","vendor":"atlassian"},{"product":"jira_software_data_center","vendor":"atlassian"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[],"description":"Affected versions of Atlassian Jira Server and Data Center allow remote attackers to access sensitive information without being authenticated in the Global permissions screen. The affected versions are before version 8.8.0.","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":"Information disclosure in Jira Server","id":"CVE-2019-20898","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"atlassian:jira","products":["atlassian:jira"],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in Jira Server","id":"CVE-2019-20899"},"packages":[],"prev":{"headline":"File upload in Jira Server","id":"CVE-2019-20897"},"products":["Jira Server"],"published":"2020-07-13","related":[{"cvss_score":9.8,"headline":"Deserialization in Jira Server","id":"CVE-2020-14172","kev_date_added":null,"published":"2020-07-03"},{"cvss_score":9.8,"headline":"Code injection in Jira Server","id":"CVE-2019-20409","kev_date_added":null,"published":"2020-06-23"},{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2017-5983","kev_date_added":null,"published":"2017-04-10"},{"cvss_score":9,"headline":"Code injection in n/a","id":"CVE-2010-1165","kev_date_added":null,"published":"2010-04-20"},{"cvss_score":8.8,"headline":"Cross-site request forgery in Atlassian JIRA Server before 7.1.9","id":"CVE-2016-4319","kev_date_added":null,"published":"2017-04-10"},{"cvss_score":8.1,"headline":"Auth bypass in Jira","id":"CVE-2019-8443","kev_date_added":null,"published":"2019-05-22"},{"cvss_score":7.5,"headline":"Information disclosure in Jira Data Center","id":"CVE-2021-41305","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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["Atlassian"]},"summary":"Remote attackers can access sensitive information in the Global permissions screen without authentication, requiring an upgrade to Jira Server.","url":"https://insights.sbomify.com/CVE-2019-20898/"}