{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2018-13404 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-13404 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-13404 is a medium-severity server-side request forgery vulnerability in Atlassian Jira, published on 13 Feb 2019. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-13404 and fix it if it is affected.\n\nWhat it is: CVE-2018-13404 is a medium-severity server-side request forgery vulnerability in Atlassian Jira, published on 13 Feb 2019. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-13404 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-2018-13404/ (Markdown: https://insights.sbomify.com/CVE-2018-13404/index.md)","id":"CVE-2018-13404","markdown":"https://insights.sbomify.com/CVE-2018-13404/index.md","name":"CVE-2018-13404","record":{"aliases":["GHSA-5pg5-2rp3-4hw8"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Atlassian Jira","requires_auth":"high_privilege","summary":"Administrators can exploit an SSRF vulnerability in Jira to scan internal networks and access internal service information.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"atlassian","cpe":[{"product":"jira","vendor":"atlassian"},{"product":"jira_server","vendor":"atlassian"}],"cvss":{"score":4.1,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"The VerifyPopServerConnection resource in Atlassian Jira before version 7.6.10, from version 7.7.0 before version 7.7.5, from version 7.8.0 before version 7.8.5, from version 7.9.0 before version 7.9.3, from version 7.10.0 before version 7.10.3, from version 7.11.0 before version 7.11.3, from version 7.12.0 before version 7.12.3, and from version 7.13.0 before version 7.13.1 allows remote attackers who have administrator rights to determine the existence of internal hosts \u0026 open ports and in some cases obtain service information from internal network resources via a Server Side Request Forgery (SSRF) 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":"Server-side request forgery in Jira","id":"CVE-2018-13404","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"atlassian:jira","products":["atlassian:jira","atlassian:jira_server"],"type":"ssrf","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2018-13405"},"packages":[],"prev":{"headline":"Cross-site scripting in Jira","id":"CVE-2018-13403"},"products":["Jira"],"published":"2019-02-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":"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 an SSRF vulnerability in Jira to scan internal networks and access internal service information.","url":"https://insights.sbomify.com/CVE-2018-13404/"}