Glib: integer overflow leading to buffer underflow and out-of-bounds write in glib g_base64_encode()
- 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 the GLib Base64 encoding routine when processing very large input data. Due to incorrect use of integer types during length calculation, the library may miscalculate buffer boundaries. This can cause memory writes outside the allocated buffer. Applications that process untrusted or extremely large Base64 input using GLib may crash or behave unpredictably.
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