{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-14995 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-14995 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-14995 is a medium-severity missing authorization vulnerability in Atlassian Jira Server, published on 11 Sep 2019. 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-14995 and fix it if it is affected.\n\nWhat it is: CVE-2019-14995 is a medium-severity missing authorization vulnerability in Atlassian Jira Server, published on 11 Sep 2019. 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-14995 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-14995/ (Markdown: https://insights.sbomify.com/CVE-2019-14995/index.md)","id":"CVE-2019-14995","markdown":"https://insights.sbomify.com/CVE-2019-14995/index.md","name":"CVE-2019-14995","record":{"aliases":["GHSA-qr6q-3xcr-gfvw"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jira issue tracker","requires_auth":"none","summary":"Remote attackers can determine if specific attachments exist and validate issue keys in Jira due to missing permission checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"atlassian","cpe":[{"product":"jira_server","vendor":"atlassian"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"The /rest/api/1.0/render resource in Jira before version 8.4.0 allows remote anonymous attackers to determine if an attachment with a specific name exists and if an issue key is valid via a missing permissions check.","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","id":"CVE-2019-14995","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"atlassian:jira_server","products":["atlassian:jira_server"],"type":"missing_authorization","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in Jira","id":"CVE-2019-14996"},"packages":[],"prev":{"headline":"Path traversal in Jira Service Desk Data Center","id":"CVE-2019-14994"},"products":["Jira"],"published":"2019-09-11","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 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":"Remote attackers can determine if specific attachments exist and validate issue keys in Jira due to missing permission checks.","url":"https://insights.sbomify.com/CVE-2019-14995/"}