{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-18096 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-18096 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-18096 is a high-severity server-side request forgery vulnerability in Atlassian Application Links, published on 4 Apr 2018. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-18096 and fix it if it is affected.\n\nWhat it is: CVE-2017-18096 is a high-severity server-side request forgery vulnerability in Atlassian Application Links, published on 4 Apr 2018. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-18096 in the wild and no public exploit code.\n\nAffected product: Atlassian Application Links. 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-2017-18096/ (Markdown: https://insights.sbomify.com/CVE-2017-18096/index.md)","id":"CVE-2017-18096","markdown":"https://insights.sbomify.com/CVE-2017-18096/index.md","name":"CVE-2017-18096","record":{"aliases":["GHSA-3jwg-839p-m5gf"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Atlassian Application Links","requires_auth":"high_privilege","summary":"Administrators can exploit SSRF in Atlassian Application Links to access internal network resources and cloud metadata credentials.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"atlassian","cpe":[{"product":"application_links","vendor":"atlassian"}],"cvss":{"score":7.2,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"The OAuth status rest resource in Atlassian Application Links before version 5.2.7, from 5.3.0 before 5.3.4 and from 5.4.0 before 5.4.3 allows remote attackers with administrative rights to access the content of internal network resources via a Server Side Request Forgery (SSRF) by creating an OAuth application link to a location they control and then redirecting access from the linked location's OAuth status rest resource to an internal location. When running in an environment like Amazon EC2, this flaw maybe used to access to a metadata resource that provides access credentials and other potentially confidential information.","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":"Server-side request forgery in Atlassian Application Links","id":"CVE-2017-18096","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in Jira","id":"CVE-2017-18097"},"packages":[],"prev":{"headline":"Missing authorization in Crucible","id":"CVE-2017-18095"},"products":["Atlassian Application Links"],"published":"2018-04-04","related":[{"cvss_score":8.7,"headline":"XML external entity in Application Links","id":"CVE-2017-18111","kev_date_added":null,"published":"2019-03-29"},{"cvss_score":6.1,"headline":"Cross-site scripting in Application Links","id":"CVE-2017-16860","kev_date_added":null,"published":"2018-05-14"},{"cvss_score":5.4,"headline":"Cross-site scripting in Atlassian Application Links","id":"CVE-2018-20239","kev_date_added":null,"published":"2019-04-30"},{"cvss_score":4.9,"headline":"Missing authorization in Application Links","id":"CVE-2019-20105","kev_date_added":null,"published":"2020-03-17"},{"cvss_score":4.8,"headline":"Cross-site scripting in Atlassian Application Links","id":"CVE-2018-5227","kev_date_added":null,"published":"2018-04-10"},{"cvss_score":4.3,"headline":"Missing authorization in Application Links","id":"CVE-2019-15011","kev_date_added":null,"published":"2019-12-17"}],"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":"Administrators can exploit SSRF in Atlassian Application Links to access internal network resources and cloud metadata credentials.","url":"https://insights.sbomify.com/CVE-2017-18096/"}