{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-15004 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-15004 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-15004 is a high-severity path traversal vulnerability in Atlassian Jira Service Desk Data Center, published on 7 Nov 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-15004 and fix it if it is affected.\n\nWhat it is: CVE-2019-15004 is a high-severity path traversal vulnerability in Atlassian Jira Service Desk Data Center, published on 7 Nov 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-15004 in the wild and no public exploit code.\n\nAffected product: Atlassian Jira Service Desk 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-15004/ (Markdown: https://insights.sbomify.com/CVE-2019-15004/index.md)","id":"CVE-2019-15004","markdown":"https://insights.sbomify.com/CVE-2019-15004/index.md","name":"CVE-2019-15004","record":{"aliases":["GHSA-6qgm-96gr-qq5m"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Jira Service Desk","requires_auth":"none","summary":"Remote attackers with portal access can view arbitrary issues in Jira Service Desk projects via a path traversal vulnerability.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"atlassian","cpe":[{"product":"jira_service_desk","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":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"The Customer Context Filter in Atlassian Jira Service Desk Server and Jira Service Desk Data Center before 3.9.17, from 3.10.0 before 3.16.10, from 4.0.0 before 4.2.6, from 4.3.0 before 4.3.5, from 4.4.0 before 4.4.3, and from 4.5.0 before 4.5.1 allows remote attackers with portal access to view arbitrary issues in Jira Service Desk projects via a path traversal vulnerability. Note that when the 'Anyone can email the service desk or raise a request in the portal' setting is enabled, an attacker can grant themselves portal access, allowing them to exploit the 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":"Path traversal in Jira Service Desk Data Center","id":"CVE-2019-15004","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Missing authorization in Bamboo","id":"CVE-2019-15005"},"packages":[],"prev":{"headline":"Missing authorization in Jira Service Desk Data Center","id":"CVE-2019-15003"},"products":["Jira Service Desk Data Center","Jira Service Desk Server"],"published":"2019-11-07","related":[{"cvss_score":7.5,"headline":"Path traversal in Jira Service Desk Data Center","id":"CVE-2019-14994","kev_date_added":null,"published":"2019-09-19"},{"cvss_score":7.2,"headline":"Code injection in Jira Service Desk Data Center","id":"CVE-2021-39115","kev_date_added":null,"published":"2021-09-01"},{"cvss_score":5.7,"headline":"Server-side request forgery in Jira Service Management Data Center","id":"CVE-2021-43959","kev_date_added":null,"published":"2022-07-26"},{"cvss_score":5.3,"headline":"Missing authorization in Jira Service Desk Data Center","id":"CVE-2019-15003","kev_date_added":null,"published":"2019-11-07"},{"cvss_score":4.8,"headline":"Cross-site scripting in Jira Service Desk Server and Data Center","id":"CVE-2020-14166","kev_date_added":null,"published":"2020-07-01"},{"cvss_score":4.3,"headline":"Information disclosure in Jira Service Desk Server","id":"CVE-2020-14180","kev_date_added":null,"published":"2020-09-21"}],"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 with portal access can view arbitrary issues in Jira Service Desk projects via a path traversal vulnerability.","url":"https://insights.sbomify.com/CVE-2019-15004/"}