Application crash via GString size calculation overflow
Published Jun 13, 2025 · Updated Jun 2, 2026
Integer overflow in GString expansion in GLib allows remote attackers to crash dependent applications via oversized string input. g_string_maybe_expand() adds the existing length to the requested expansion without first rejecting gsize wraparound, leading to an undersized allocation and a subsequent out-of-bounds write. Triggering the flaw requires a caller to build a string near the address-space limit and then append attacker-controlled data; the bounded reported consequence is a crash or memory corruption.
Summary
What happened
Integer overflow in GString expansion in GLib allows remote attackers to crash dependent applications via oversized string input. g_string_maybe_expand() adds the existing length to the requested expansion without first rejecting gsize wraparound, leading to an undersized allocation and a subsequent out-of-bounds write. Triggering the flaw requires a caller to build a string near the address-space limit and then append attacker-controlled data; the bounded reported consequence is a crash or memory corruption.
The record
- CVE
- CVE-2025-6052
- Published
- Jun 13, 2025
- Updated
- Jun 2, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Enterprise Linux 10
- Classifications
- CWE-190, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 13, 2025CVE publishedPublication date reported by the CVE source.
- Jun 2, 2026Record 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
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.
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