{"answers":{"affected":"It affects 4 products.","exploited":"There is no known exploitation of CVE-2020-4029 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-4029 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-4029 is a medium-severity missing authorization vulnerability in Atlassian Jira, published on 1 Jul 2020. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-4029 and fix it if it is affected.\n\nWhat it is: CVE-2020-4029 is a medium-severity missing authorization vulnerability in Atlassian Jira, published on 1 Jul 2020. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-4029 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-2020-4029/ (Markdown: https://insights.sbomify.com/CVE-2020-4029/index.md)","id":"CVE-2020-4029","markdown":"https://insights.sbomify.com/CVE-2020-4029/index.md","name":"CVE-2020-4029","record":{"aliases":["GHSA-w67p-2w4g-fgjp"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jira Server","requires_auth":"low_privilege","summary":"Remote attackers can enumerate project names in Atlassian Jira Server due to improper authorization checks on a specific REST resource.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"atlassian","cpe":[{"product":"jira","vendor":"atlassian"},{"product":"jira_data_center","vendor":"atlassian"},{"product":"jira_server","vendor":"atlassian"},{"product":"jira_software_data_center","vendor":"atlassian"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[],"description":"The /rest/project-templates/1.0/createshared resource in Atlassian Jira Server and Data Center before version 8.5.5, from 8.6.0 before 8.7.2, and from 8.8.0 before 8.8.1 allows remote attackers to enumerate project names via an improper authorization 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":"Missing authorization in Jira Server and Data Center","id":"CVE-2020-4029","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"atlassian:jira","products":["atlassian:jira","atlassian:jira_data_center","atlassian:jira_server"],"type":"missing_authorization","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"OOB read in `TrioParse` in FreeRDP","id":"CVE-2020-4030"},"packages":[],"prev":{"headline":"Information disclosure in Jira Server and Data Center","id":"CVE-2020-4028"},"products":["Jira Server and Data Center"],"published":"2020-07-01","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 enumerate project names in Atlassian Jira Server due to improper authorization checks on a specific REST resource.","url":"https://insights.sbomify.com/CVE-2020-4029/"}