{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-1789 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-1789 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-1789 is a high-severity server-side request forgery vulnerability in Ibm Api Connect, published on 7 Sep 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-1789 and fix it if it is affected.\n\nWhat it is: CVE-2018-1789 is a high-severity server-side request forgery vulnerability in Ibm Api Connect, published on 7 Sep 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-1789 in the wild and no public exploit code.\n\nAffected product: Ibm Api Connect. 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-1789/ (Markdown: https://insights.sbomify.com/CVE-2018-1789/index.md)","id":"CVE-2018-1789","markdown":"https://insights.sbomify.com/CVE-2018-1789/index.md","name":"CVE-2018-1789","record":{"aliases":["GHSA-c3j4-jv4j-wgmf"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM API Connect","requires_auth":"low_privilege","summary":"An attacker can exploit a server-side request forgery vulnerability in IBM API Connect to send crafted requests, potentially accessing internal resources.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"api_connect","vendor":"ibm"}],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:3.0/A:L/AC:H/AV:N/C:H/I:H/PR:L/S:C/UI:N/E:U/RC:C/RL:O","version":"3.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"IBM API Connect v2018.1.0 through v2018.3.4 could allow an attacker to send a specially crafted request to conduct a server side request forgery attack. IBM X-Force ID: 148939.","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 API Connect","id":"CVE-2018-1789","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:api_connect","products":["ibm:api_connect"],"type":"ssrf","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site request forgery in Financial Transaction Manager","id":"CVE-2018-1790"},"packages":[],"prev":{"headline":"Information disclosure in Spectrum Protect","id":"CVE-2018-1788"},"products":["API Connect"],"published":"2018-09-07","related":[{"cvss_score":10,"headline":"Command injection in API Connect","id":"CVE-2019-4202","kev_date_added":null,"published":"2019-04-15"},{"cvss_score":9.8,"headline":"Authentication bypass in IBM API Connect","id":"CVE-2025-13915","kev_date_added":null,"published":"2025-12-26"},{"cvss_score":9.8,"headline":"Command injection in API Connect","id":"CVE-2018-1469","kev_date_added":null,"published":"2018-04-04"},{"cvss_score":9.1,"headline":"IBM API Connect SQL Injection","id":"CVE-2026-9074","kev_date_added":null,"published":"2026-07-08"},{"cvss_score":9,"headline":"Information disclosure in API Connect","id":"CVE-2019-4008","kev_date_added":null,"published":"2019-02-07"},{"cvss_score":8.9,"headline":"Server-side request forgery in API Connect","id":"CVE-2019-4203","kev_date_added":null,"published":"2019-04-15"},{"cvss_score":8.9,"headline":"Code injection in API Connect","id":"CVE-2018-1774","kev_date_added":null,"published":"2018-11-09"}],"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-17","vendors":["IBM"]},"summary":"An attacker can exploit a server-side request forgery vulnerability in IBM API Connect to send crafted requests, potentially accessing internal resources.","url":"https://insights.sbomify.com/CVE-2018-1789/"}