Memory disclosure via zero-length UCS-2 conversion
Published Mar 11, 2025 · Updated Mar 11, 2025
Uninitialized heap read in ZVBI before 0.2.44 allows remote attackers to disclose process memory through a zero-length UCS-2 conversion. In src/conv.c, vbi_strndup_iconv_ucs2 accepted a zero src_length and continued into conversion; the patch returns NULL first to prevent the uninitialized read. The affected call must receive a zero-length UCS-2 input, and the published record reports memory disclosure without integrity or service impact.
Summary
What happened
Uninitialized heap read in ZVBI before 0.2.44 allows remote attackers to disclose process memory through a zero-length UCS-2 conversion. In src/conv.c, vbi_strndup_iconv_ucs2 accepted a zero src_length and continued into conversion; the patch returns NULL first to prevent the uninitialized read. The affected call must receive a zero-length UCS-2 input, and the published record reports memory disclosure without integrity or service impact.
The record
- CVE
- CVE-2025-2173
- Published
- Mar 11, 2025
- Updated
- Mar 11, 2025
- Vendor
- zapping-vbi
- Product
- ZVBI
- Classifications
- CWE-824, CWE-908
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 11, 2025CVE publishedPublication date reported by the CVE source.
- Mar 11, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.2.0
- Affected versionversion=0.2.1
- Affected versionversion=0.2.10
- Affected versionversion=0.2.11
- Affected versionversion=0.2.12
- Affected versionversion=0.2.13
- Affected versionversion=0.2.14
- Affected versionversion=0.2.15
- Affected versionversion=0.2.16
- Affected versionversion=0.2.17
- Affected versionversion=0.2.18
- Affected versionversion=0.2.19
- Affected versionversion=0.2.2
- Affected versionversion=0.2.20
- Affected versionversion=0.2.21
- Affected versionversion=0.2.22
- Affected versionversion=0.2.23
- Affected versionversion=0.2.24
- Affected versionversion=0.2.25
- Affected versionversion=0.2.26
- Affected versionversion=0.2.27
- Affected versionversion=0.2.28
- Affected versionversion=0.2.29
- Affected versionversion=0.2.3
- Affected versionversion=0.2.30
- Affected versionversion=0.2.31
- Affected versionversion=0.2.32
- Affected versionversion=0.2.33
- Affected versionversion=0.2.34
- Affected versionversion=0.2.35
- Affected versionversion=0.2.36
- Affected versionversion=0.2.37
- Affected versionversion=0.2.38
- Affected versionversion=0.2.39
- Affected versionversion=0.2.4
- Affected versionversion=0.2.40
- Affected versionversion=0.2.41
- Affected versionversion=0.2.42
- Affected versionversion=0.2.43
- Affected versionversion=0.2.5
- Affected versionversion=0.2.6
- Affected versionversion=0.2.7
- Affected versionversion=0.2.8
- Affected versionversion=0.2.9
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo