# CVE-2018-1778: Auth bypass in API Connect

> Attackers can bypass authentication and gain unauthorized access to user data and privileges if the AccessToken Model is exposed via REST API.

- **Severity:** High 7.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Dec 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-gpvh-xcx4-jwmg

## What is CVE-2018-1778?

CVE-2018-1778 is a high-severity authentication bypass vulnerability in Ibm Api Connect, published on 20 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

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

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2018-1778?

It affects 1 product.


Products: Ibm Api Connect.

## How do I fix CVE-2018-1778?

No fix has been published for CVE-2018-1778 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-1778 being exploited?

There is no known exploitation of CVE-2018-1778 in the wild and no public exploit code.

## Other vulnerabilities in Ibm Api Connect

- [CVE-2019-4202](https://insights.sbomify.com/CVE-2019-4202/): Command injection in API Connect (critical 10.0)
- [CVE-2025-13915](https://insights.sbomify.com/CVE-2025-13915/): Authentication bypass in IBM API Connect (critical 9.8)
- [CVE-2018-1469](https://insights.sbomify.com/CVE-2018-1469/): Command injection in API Connect (critical 9.8)
- [CVE-2026-9074](https://insights.sbomify.com/CVE-2026-9074/): IBM API Connect SQL Injection (critical 9.1)
- [CVE-2019-4008](https://insights.sbomify.com/CVE-2019-4008/): Information disclosure in API Connect (critical 9.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1778 and fix it if it is affected.

What it is: CVE-2018-1778 is a high-severity authentication bypass vulnerability in Ibm Api Connect, published on 20 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-1778 in the wild and no public exploit code.

Affected product: Ibm Api Connect. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-1778/ (Markdown: https://insights.sbomify.com/CVE-2018-1778/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-1778
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-1778
- OSV: https://osv.dev/vulnerability/CVE-2018-1778

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-1778/
Summaries are generated and may contain mistakes; the official description above is the record.
