# CVE-2024-56468: IBM InfoSphere Data Replication VSAM for z/OS Remote Source denial of service

> A remote attacker can cause a denial of service in IBM InfoSphere Data Replication by sending an invalid HTTP request to the log reading service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jul 2025
- **Updated:** 24 Aug 2025
- **Also known as:** GHSA-3j2r-4m5c-xw29

## What is CVE-2024-56468?

CVE-2024-56468 is a high-severity denial of service vulnerability in IBM InfoSphere Data Replication VSAM for z/OS Remote Source, published on 8 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

IBM InfoSphere Data Replication VSAM for z/OS Remote Source 11.4 could allow a remote user to cause a denial of service by sending an invalid HTTP request to the log reading service.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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

It affects 1 product.


Products: Ibm Infosphere Data Replication.

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

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

## Is CVE-2024-56468 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-56468 is a high-severity denial of service vulnerability in IBM InfoSphere Data Replication VSAM for z/OS Remote Source, published on 8 Jul 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-56468 in the wild and no public exploit code.

Affected product: IBM InfoSphere Data Replication VSAM for z/OS Remote Source. 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-56468/ (Markdown: https://insights.sbomify.com/CVE-2024-56468/index.md)
```

## Sources

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

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