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.
 mdeslaur> upstream has closed this bug as "won't fix". Let's ignore this.
 tyhicks> upstream has now fixed this CVE so I'm un-ignoring it. We need to
  verify but we don't think we are vulnerable as we're already disabling the
  stack trace.
Ubuntu 12.04 ESM (Precise Pangolin):needs-triage
Ubuntu 14.04 ESM (Trusty Tahr):needs-triage
Ubuntu 16.04 LTS (Xenial Xerus):DNE
Ubuntu 18.04 LTS (Bionic Beaver):DNE
Ubuntu 19.04 (Disco Dingo):DNE
Ubuntu 19.10 (Eoan):DNE
Source: glibc (LP Ubuntu Debian)
Upstream:released (2.26)
Ubuntu 12.04 ESM (Precise Pangolin):DNE
Ubuntu 14.04 ESM (Trusty Tahr):DNE
Ubuntu 16.04 LTS (Xenial Xerus):needs-triage
Ubuntu 18.04 LTS (Bionic Beaver):not-affected (2.27-3ubuntu1)
Ubuntu 19.04 (Disco Dingo):not-affected (2.29-0ubuntu2)
Ubuntu 19.10 (Eoan):not-affected (2.29-0ubuntu2)
More Information

Updated: 2019-09-19 14:14:31 UTC (commit d32ebc32606b9517c6fa7d65a15441e2a57a6de5)