Glib: integer overflow in g_string_maybe_expand() leading to potential buffer overflow in glib gstring
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
A flaw was found in how GLib’s GString manages memory when adding data to strings. If a string is already very large, combining it with more input can cause a hidden overflow in the size calculation. This makes the system think it has enough memory when it doesn’t. As a result, data may be written past the end of the allocated memory, leading to crashes or memory corruption.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- bootc
Version range not reported
- glib2
Version range not reported
- glycin-loaders
Version range not reported
- loupe
Version range not reported
- mingw-glib2
Version range not reported
- rpm-ostree
Version range not reported
- glib2
Version range not reported
- glib2
Version range not reported
- glib2
Version range not reported
- librsvg2
Version range not reported
- mingw-glib2
Version range not reported
- bootc
Version range not reported
- glib2
Version range not reported
- librsvg2
Version range not reported
- mingw-glib2
Version range not reported