# CVE-2024-47113: IBM ICP - Voice Gateway XML injection

> Remote attackers can exploit XML injection in IBM Voice Gateway to view or modify XML document information.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jan 2025
- **Updated:** 21 Jan 2025
- **Also known as:** GHSA-3x55-3v35-wg88

## What is CVE-2024-47113?

CVE-2024-47113 is a high-severity vulnerability in IBM Voice Gateway, published on 18 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM ICP - Voice Gateway 1.0.2, 1.0.2.4, 1.0.3, 1.0.4, 1.0.5, 1.0.6. 1.0.7, 1.0.7.1, and 1.0.8 could allow remote attacker to send specially crafted XML statements, which would allow them to attacker to view or modify information in the XML document.

Weakness: CWE-91 (XML Injection)

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

It affects 1 product.


Products: Ibm Voice Gateway.

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

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

## Is CVE-2024-47113 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-47113 is a high-severity vulnerability in IBM Voice Gateway, published on 18 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-47113 in the wild and no public exploit code.

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

## Sources

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

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