# CVE-2021-45968: Server-side request forgery in n/a

> An SSRF vulnerability in the Pascom Cloud Phone System backend allows attackers to interact with internal network resources via the Tomcat server.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 18 Mar 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-x28m-8977-r45c

## What is CVE-2021-45968?

CVE-2021-45968 is a high-severity server-side request forgery vulnerability in n/a, published on 18 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in xmppserver jar in the XMPP Server component of the JIve platform, as used in Pascom Cloud Phone System before 7.20.x (and in other products). An endpoint in the backend Tomcat server of the Pascom allows SSRF, a related issue to CVE-2019-18394.

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

## Which versions are affected by CVE-2021-45968?

It affects 2 products.


Products: Jivesoftware Jive, Pascom Cloud Phone System.

## How do I fix CVE-2021-45968?

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

## Is CVE-2021-45968 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-45968 exists.

Public exploit code:

- Pascom CPS - Local File Inclusion (nuclei): http/cves/2021/CVE-2021-45968.yaml

## Other vulnerabilities in n/a

- [CVE-2016-4334](https://insights.sbomify.com/CVE-2016-4334/): Open redirect in Jive before 2016.3.1 (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-45968 and fix it if it is affected.

What it is: CVE-2021-45968 is a high-severity server-side request forgery vulnerability in n/a, published on 18 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-45968 exists.

Affected product: n/a. 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-2021-45968/ (Markdown: https://insights.sbomify.com/CVE-2021-45968/index.md)
```

## Sources

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

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