CVE-2025-6052
BaseFortify
Publication date: 2025-06-13
Last updated on: 2025-08-20
Assigner: Red Hat, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| gnome | glib | From 2.75.3 (inc) to 2.84.3 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-190 | The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an integer overflow in the GLib library's GString function g_string_maybe_expand(). When very large strings are appended with more data, the internal size calculation can overflow, causing the function to mistakenly believe there is enough buffer space. This leads to a buffer overflow where data is written beyond the allocated memory, potentially causing memory corruption or application crashes. [1]
How can this vulnerability impact me? :
The vulnerability can cause applications using GLib's GString to crash or experience memory corruption if they process very large strings with appended data. Although exploitation is difficult due to the large memory requirements, it could be triggered remotely if an application processes large untrusted input using GString operations, potentially leading to denial of service or instability. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves identifying if your system is running a vulnerable version of the GLib library (versions 2.75.3 up to 2.84.3) and monitoring applications that use GString operations with large input data. There are no specific commands provided to detect exploitation attempts or presence of the vulnerability directly. However, you can check the installed GLib version using commands like 'pkg-config --modversion glib-2.0' or 'rpm -q glib2' on RPM-based systems. Monitoring application logs for crashes or memory corruption related to string operations may also help detect issues. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the GLib library to a fixed version beyond 2.84.3 where the vulnerability is resolved. If updating is not immediately possible, avoid processing extremely large strings or untrusted input with GString operations in your applications. Additionally, apply any vendor patches or advisories related to this CVE as soon as they become available. [1]