# CVE-2022-22416: Server-side request forgery in Sterling Partner Engagement Manager

> An authenticated attacker can exploit SSRF in IBM Sterling Partner Engagement Manager to send unauthorized requests, enabling network enumeration and further attacks.

- **Severity:** Medium 5.4 (`CVSS:3.0/UI:N/AV:N/PR:L/C:L/S:U/A:N/I:L/AC:L/E:U/RC:C/RL:O`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jul 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-p3qc-mh98-4vq5

## What is CVE-2022-22416?

CVE-2022-22416 is a medium-severity server-side request forgery vulnerability in IBM Sterling Partner Engagement Manager, published on 19 Jul 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM Sterling Partner Engagement Manager 6.1.2, 6.2, and Cloud/SasS 22.2 is vulnerable to server-side request forgery (SSRF). This may allow an authenticated attacker to send unauthorized requests from the system, potentially leading to network enumeration or facilitating other attacks. IBM X-Force ID: 223126.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 2 products.


Products: Ibm Partner Engagement Manager, Ibm Partner Engagement Manager on Cloud\/Saas.

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

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

## Is CVE-2022-22416 being exploited?

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

## Other vulnerabilities in IBM Sterling Partner Engagement Manager

- [CVE-2021-29781](https://insights.sbomify.com/CVE-2021-29781/): Deserialization in Partner Engagement Manager (critical 9.8)
- [CVE-2022-22360](https://insights.sbomify.com/CVE-2022-22360/): Other in Sterling Partner Engagement Manager (high 7.5)
- [CVE-2022-22358](https://insights.sbomify.com/CVE-2022-22358/): XML external entity in Sterling Partner Engagement Manager (high 7.1)
- [CVE-2022-22328](https://insights.sbomify.com/CVE-2022-22328/): Privilege escalation in SterlingPartner Engagement Manager (medium 6.2)
- [CVE-2022-22332](https://insights.sbomify.com/CVE-2022-22332/): Security feature bypass in Sterling Partner Engagement Manager (medium 5.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-22416 and fix it if it is affected.

What it is: CVE-2022-22416 is a medium-severity server-side request forgery vulnerability in IBM Sterling Partner Engagement Manager, published on 19 Jul 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-22416 in the wild and no public exploit code.

Affected product: IBM Sterling Partner Engagement Manager. 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-22416/ (Markdown: https://insights.sbomify.com/CVE-2022-22416/index.md)
```

## Sources

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

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