# CVE-2024-22347: IBM UrbanCode Velocity information disclosure

> Weak cryptographic algorithms in IBM DevOps Velocity allow attackers to decrypt highly sensitive information.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/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:** 20 Jan 2025
- **Updated:** 21 Jan 2025
- **Also known as:** GHSA-x8gx-r9p5-6xp8

## What is CVE-2024-22347?

CVE-2024-22347 is a medium-severity vulnerability in IBM DevOps Velocity, published on 20 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

IBM DevOps Velocity 5.0.0 and IBM UrbanCode Velocity 4.0.0 through 4.0. 25 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.

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

## Which versions are affected by CVE-2024-22347?

It affects 2 products.


Products: Hcltech Devops Velocity, Ibm Urbancode Velocity.

## How do I fix CVE-2024-22347?

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

## Is CVE-2024-22347 being exploited?

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

## Other vulnerabilities in IBM DevOps Velocity

- [CVE-2025-31991](https://insights.sbomify.com/CVE-2025-31991/): HCL DevOps Velocity is susceptible to brute-force attacks (medium 6.8)
- [CVE-2024-22348](https://insights.sbomify.com/CVE-2024-22348/): IBM UrbanCode Velocity cross-origin resource sharing (medium 5.3)
- [CVE-2024-22349](https://insights.sbomify.com/CVE-2024-22349/): IBM UrbanCode Velocity information disclosure (medium 4.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-22347 and fix it if it is affected.

What it is: CVE-2024-22347 is a medium-severity vulnerability in IBM DevOps Velocity, published on 20 Jan 2025. 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-2024-22347 in the wild and no public exploit code.

Affected product: IBM DevOps Velocity. 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-2024-22347/ (Markdown: https://insights.sbomify.com/CVE-2024-22347/index.md)
```

## Sources

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

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