Cyber Resilience

CVE-2024-47113

Ibm Voice Gateway 1.0.2 … 1.0.8

Published
18 January 2025
Modified
18 August 2025
Patch / advisory
CVSS Score v3.1 8.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
EPSS Score 0.0060 46th percentile
Risk Priority 60 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-47113 is a high-severity aka Blind XPath Injection (CWE-91) vulnerability in Ibm Voice Gateway. Its CVSS base score is 8.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 46th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2024-47113 is an XML injection vulnerability (CWE-91) affecting IBM ICP Voice Gateway versions 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. It enables a remote attacker to send specially crafted XML statements, allowing them to view or modify information within the XML document. The vulnerability carries a CVSS v3.1 base score of 8.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N), indicating high severity due to its network accessibility, low attack complexity, and significant impacts on confidentiality and integrity.

An attacker with low privileges (PR:L) can exploit this vulnerability remotely over the network without requiring user interaction. Successful exploitation allows the attacker to read sensitive data or alter XML content, potentially leading to unauthorized data exposure or manipulation within the affected Voice Gateway component.

The IBM security advisory at https://www.ibm.com/support/pages/node/7175791 provides details on mitigation, including available patches and recommended actions for affected versions.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-13096Same vendor: Ibm
CVE-2026-11169Shared CWE-91
CVE-2023-35016Same vendor: Ibm
CVE-2025-54251Shared CWE-91
CVE-2024-51451Same vendor: Ibm
CVE-2024-25413Shared CWE-91
CVE-2024-51454Same vendor: Ibm
CVE-2024-39736Same vendor: Ibm
CVE-2025-36324Same vendor: Ibm
CVE-2025-14290Same vendor: Ibm

Affected Assets

ibm
voice gateway
1.0.2, 1.0.2.4, 1.0.3, 1.0.4, 1.0.5

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Input validation directly stops unneutralized XML metacharacters from reaching the parser.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC directly requires input neutralization and validation that eliminates XML injection flaws.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing catches XML injection during development but does not itself implement the fix.

A.8.15 Logging partial match
finds

Logging can record injection attempts for detection but does not prevent the weakness.

finds

Monitoring can detect exploitation but provides no preventive control over XML handling.

prevents

Secure SDLC mandates input validation and output encoding that directly prevent XML injection.

prevents

Application security requirements explicitly call for defenses against injection flaws including XML.

prevents

Secure architecture principles reduce attack surface but do not prescribe XML-specific controls.

References