It was found that the malloc fallback logic when running *scanf() does not have happen at the precise moment (scanf choses between heap and stack), this can lead to a stack-overflow in certain configurations. Reference: https://security-tracker.debian.org/tracker/CVE-2015-1473
This report is a duplicate of bug 1188235 - (CVE-2015-1472) CVE-2015-1472 glibc: heap buffer overflow in glibc swscanf.
(In reply to Martin Sebor from comment #2) > This report is a duplicate of bug 1188235 - (CVE-2015-1472) CVE-2015-1472 > glibc: heap buffer overflow in glibc swscanf. Not as per debian, see difference between: https://security-tracker.debian.org/tracker/CVE-2015-1472 and https://security-tracker.debian.org/tracker/CVE-2015-1473
(In reply to Huzaifa S. Sidhpurwala from comment #3) > Not as per debian, see difference between: > > https://security-tracker.debian.org/tracker/CVE-2015-1472 and > https://security-tracker.debian.org/tracker/CVE-2015-1473 Sorry, I don't see it. The upstream bug and fix are the same in both: Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=16618 Fix: https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=5bd80bfe9ca0d955bfbbc002781bc7b01b6bcb06
Statement: This issue does not affect the version of glibc package as shipped with Red Hat Enterprise Linux 5 and 6.
This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2015:2199 https://rhn.redhat.com/errata/RHSA-2015-2199.html
This issue has been addressed in the following products: Red Hat Enterprise Linux 7.1 EUS - Server and Compute Node Only Red Hat Enterprise Linux 7.1 EUS - Server and Compute Node Only Via RHSA-2015:2589 https://rhn.redhat.com/errata/RHSA-2015-2589.html