# CVE-2022-22313: IBM QRadar Data Synchronization App information disclosure

> Weak cryptographic algorithms in IBM QRadar Data Synchronization App allow attackers to decrypt highly sensitive information.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 May 2023
- **Updated:** 29 Jan 2025
- **Also known as:** GHSA-w8g3-3xjr-4mq8

## What is CVE-2022-22313?

CVE-2022-22313 is a medium-severity vulnerability in IBM QRadar Data Synchronization App, published on 6 May 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

IBM QRadar Data Synchronization App 1.0 through 3.0.1 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.  IBM X-Force ID:  217370.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

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

It affects 1 product.


Products: Ibm Qradar Data Synchronization.

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

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

## Is CVE-2022-22313 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-22313 is a medium-severity vulnerability in IBM QRadar Data Synchronization App, published on 6 May 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-22313 in the wild and no public exploit code.

Affected product: IBM QRadar Data Synchronization App. 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-22313/ (Markdown: https://insights.sbomify.com/CVE-2022-22313/index.md)
```

## Sources

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

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