# CVE-2022-41297: IBM Db2U cross-site request forgery

> An attacker can trick a trusted user into executing unauthorized actions in IBM Db2U via cross-site request forgery.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Dec 2022
- **Updated:** 24 Apr 2025
- **Also known as:** GHSA-4j45-5pwj-x33m

## What is CVE-2022-41297?

CVE-2022-41297 is a medium-severity vulnerability in IBM Db2U, published on 1 Dec 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

IBM Db2U 3.5, 4.0, and 4.5 is vulnerable to cross-site request forgery which could allow an attacker to execute malicious and unauthorized actions transmitted from a user that the website trusts.  IBM X-Force ID:  237212.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 3 products.


Products: Ibm Db2 on Cloud Pak for Data, Ibm Db2 Warehouse on Cloud Pak for Data, Ibm Db2u.

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

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

## Is CVE-2022-41297 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-41297 is a medium-severity vulnerability in IBM Db2U, published on 1 Dec 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-41297 in the wild and no public exploit code.

Affected product: IBM Db2U. 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-41297/ (Markdown: https://insights.sbomify.com/CVE-2022-41297/index.md)
```

## Sources

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

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