# CVE-2022-34350: IBM API Connect security bypass

> Remote attackers can induce server-side requests to arbitrary domains, enabling attacks on internal systems via IBM API Connect.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Feb 2023
- **Updated:** 25 Mar 2025
- **Also known as:** GHSA-434c-w883-rf5w

## What is CVE-2022-34350?

CVE-2022-34350 is a medium-severity server-side request forgery vulnerability in Ibm Api Connect, published on 8 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

IBM API Connect 10.0.0.0 through 10.0.5.0, 10.0.1.0 through 10.0.1.7, and 2018.4.1.0 through 2018.4.1.20 is vulnerable to External Service Interaction attack, caused by improper validation of user-supplied input. A remote attacker could exploit this vulnerability to induce the application to perform server-side DNS lookups or HTTP requests to arbitrary domain names. By submitting suitable payloads, an attacker can cause the application server to attack other systems that it can interact with.  IBM X-Force ID:  230264.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2022-34350?

It affects 1 product.


Products: Ibm Api Connect.

## How do I fix CVE-2022-34350?

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

## Is CVE-2022-34350 being exploited?

There is no known exploitation of CVE-2022-34350 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-2022-34350 and fix it if it is affected.

What it is: CVE-2022-34350 is a medium-severity server-side request forgery vulnerability in Ibm Api Connect, published on 8 Feb 2023. 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-2022-34350 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-2022-34350/ (Markdown: https://insights.sbomify.com/CVE-2022-34350/index.md)
```

## Sources

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

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