Certain run-time memory protection mechanisms in the GNU C Library (aka glibc or libc6) print argv[0] and backtrace information, which might allow context-dependent attackers to obtain sensitive information from process memory by executing an incorrect program, as demonstrated by a setuid program that contains a stack-based buffer overflow error, related to the __fortify_fail function in debug/fortify_fail.c, and the __stack_chk_fail (aka stack protection) and __chk_fail (aka FORTIFY_SOURCE) implementations.
Covered by Rapid7
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Suse | — | Upgrade glibc-profileUpgrade glibc-infoUpgrade glibc-32bitUpgrade glibc-i18ndataUpgrade glibc-locale-base-32bitUpgrade glibc-extraUpgrade glibc-locale-baseUpgrade libnsl1-32bitUpgrade glibc-devel-32bitUpgrade glibc-locale-32bitUpgrade glibc-devel-staticUpgrade glibc-localeUpgrade glibc-develUpgrade glibc-utilsUpgrade glibcUpgrade nscdUpgrade libnsl1Upgrade glibc-htmlUpgrade glibc-gconv-modules-extraUpgrade glibc-lang | Aug 9, 2024 | Jul 9, 2013 |
| Ubuntu | — | No solution exists | Jun 26, 2025 | Oct 14, 2010 |
Prioritize with Active Threat Intelligence
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub