Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2025-2173 is a medium-severity Access of Uninitialized Pointer (CWE-824) vulnerability in Zapping-Vbi Zvbi. Its CVSS base score is 6.9 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique OS Credential Dumping (T1003); 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 SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — 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-2025-2173 is a vulnerability in the libzvbi library versions up to 0.2.43, classified as problematic due to an uninitialized pointer issue. The flaw affects the vbi_strndup_iconv_ucs2 function in the src/conv.c file, where manipulation of the src_length argument triggers the use of an uninitialized pointer, corresponding to CWEs-824 (Access of Uninitialized Pointer) and CWE-908 (Use of Uninitialized Resource). The vulnerability carries a CVSS v3.1 base score of 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N), indicating medium severity with low confidentiality impact.
The vulnerability can be exploited remotely by unauthenticated attackers with no privileges required, as it has low attack complexity and no user interaction needed. By crafting input that manipulates the src_length parameter, an attacker can trigger the uninitialized pointer dereference, potentially leading to limited information disclosure. An exploit has been publicly disclosed and may be usable against affected libzvbi instances.
Mitigation is available through upgrading to libzvbi version 0.2.44, which addresses the issue via the patch commit 8def647eea27f7fd7ad33ff79c2d6d3e39948dce. The library maintainer was notified in advance and responded promptly and professionally, with details documented in the GitHub security advisory (GHSA-g7cg-7gw9-v8cf), release notes, and commit history.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-7526
Vulnerability Data
A vulnerability was found in libzvbi up to 0.2.43. It has been classified as problematic. Affected is the function vbi_strndup_iconv_ucs2 of the file src/conv.c. The manipulation of the argument src_length leads to uninitialized pointer. It is possible to launch the…
more
attack remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 0.2.44 is able to address this issue. The patch is identified as 8def647eea27f7fd7ad33ff79c2d6d3e39948dce. It is recommended to upgrade the affected component. The code maintainer was informed beforehand about the issues. She reacted very fast and highly professional.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover uninitialized pointer accesses through static analysis, dynamic testing, or fuzzing before deployment.
Requiring documented development processes and tools enables use of analyzers or coding standards that identify uninitialized pointer defects.
Security engineering principles can mandate memory-safety practices and language choices that structurally avoid uninitialized pointer use.
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.
Secure SDLC practices directly prevent uninitialized pointer bugs via coding standards, analysis, and reviews, but eliminating this single weakness only partially fulfills the broader control.
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.
Security testing can detect uninitialized pointer usage before release.
Secure development life cycle mandates practices that reduce uninitialized pointer defects.
Application security requirements can specify pointer initialization rules.
Secure architecture principles discourage unsafe pointer handling.
Secure coding standards directly prohibit use of uninitialized pointers.