CVE-2025-4373: Glib: buffer underflow on glib through glib/gstring.c via function g_string_insert_unichar
A flaw was found in GLib, which is vulnerable to an integer overflow in the g_string_insert_unichar() function. When the position at which to insert the character is large, the position will overflow, leading to a buffer underwrite.
Security readout for executives and security teams
Plain-English summary
CVE-2025-4373 is a GLib memory-handling bug. Under specific conditions involving a very large string insertion position, software using GLib could write before the intended buffer. The listed impact is limited integrity and availability, not data disclosure. No active exploitation is shown in the provided sources.
Executive priority
Handle through normal vulnerability management with moderate priority. This is a common-library memory corruption issue with vendor advisories available, but the provided evidence does not show active exploitation or critical impact. Prioritize exposed systems and standard platform patch cycles.
Technical view
GLib g_string_insert_unichar() can integer-overflow the insertion position, causing a buffer underwrite. The CVE maps to CWE-124 with CVSS 3.1 score 4.8: network attack vector, high complexity, no privileges or user interaction, unchanged scope, low integrity and availability impact.
Likely exposure
Exposure is most likely on systems using affected Red Hat glib2 packages in RHEL 8, 9, 10, related extended support streams, and listed Red Hat container products. Siemens advisories are referenced, but affected Siemens product details are not included in the supplied bundle.
Exploitation context
The sources do not show KEV listing or confirmed exploitation. The high attack complexity suggests exploitation depends on an application path that passes attacker-influenced values into the vulnerable GLib string operation. Treat exposure as dependency-driven rather than a directly reachable service flaw.
Researcher notes
Key uncertainty is reachability: GLib is widely used, but exploitation requires a code path that can drive a large insertion position into g_string_insert_unichar(). Validate dependency versions first, then assess application-level input paths. Do not assume all GLib consumers are practically exploitable.
Mitigation direction
Apply relevant Red Hat security advisories for affected glib2 packages.
Check GLib upstream and vendor advisories for fixed versions.
Update affected Red Hat container images listed in the source bundle.
Prioritize internet-facing applications that process untrusted string input.
Track Siemens advisories if Siemens products are in scope.
Validation and detection
Inventory installed glib2 package versions across Linux hosts.
Compare versions against affected Red Hat package builds listed for CVE-2025-4373.
Check container base images for affected glib2 builds.
Identify applications accepting untrusted input before GLib string processing.
Verify remediation through package manager or image vulnerability scan results.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-124: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-124 · source CWE mapping
Buffer Underwrite ('Buffer Underflow')
Buffer Underwrite ('Buffer Underflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.