Glib: glib: memory corruption via integer overflow in unicode case conversion
- 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 GLib. An integer overflow vulnerability in its Unicode case conversion implementation can lead to memory corruption. By processing specially crafted and extremely large Unicode strings, an attacker could trigger an undersized memory allocation, resulting in out-of-bounds writes. This could cause applications utilizing GLib for string conversion to crash or become unstable.
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
- papers
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