public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zhanghao383 at huawei dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nscd/30795] avoid snprintf using %n to generate coredump when F_S=2 is enabled
Date: Fri, 25 Aug 2023 02:36:06 +0000 [thread overview]
Message-ID: <bug-30795-131-j8JvdDnz2C@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30795-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30795
--- Comment #3 from zhanghao (ES) <zhanghao383 at huawei dot com> ---
and we find if patch 5b61880ba3a0367f8969e028cb2cfe80d6eda8ab, then check the
compilation log：
part:
[ 114s] gcc pwdcache.c -c -std=gnu11 -fgnu89-inline -O2 -g -DNDEBUG
-Wp,-D_GLIBCXX_ASSERTIONS -m64 -mtune=generic -fasynchronous-unwind-tables
-fstack-clash-protection -Wall -Wwrite-strings -Wundef -fmerge-all-constants
-frounding-math -fstack-protector-strong -fno-common -Wstrict-prototypes
-Wold-style-definition -fmath-errno -DHAVE_EPOLL -DHAVE_INOTIFY -DHAVE_NETLINK
-fpie -fcf-protection -fpie -U_FORTIFY_SOURCE -I../include
-I/home/abuild/rpmbuild/BUILD/glibc-2.34/build-x86_64-openEuler-linux/nscd
-I/home/abuild/rpmbuild/BUILD/glibc-2.34/build-x86_64-openEuler-linux
-I../sysdeps/unix/sysv/linux/x86_64/64 -I../sysdeps/unix/sysv/linux/x86_64
-I../sysdeps/unix/sysv/linux/x86/include -I../sysdeps/unix/sysv/linux/x86
-I../sysdeps/x86/nptl -I../sysdeps/unix/sysv/linux/wordsize-64
-I../sysdeps/x86_64/nptl -I../sysdeps/unix/sysv/linux/include
-I../sysdeps/unix/sysv/linux -I../sysdeps/nptl -I../sysdeps/pthread
-I../sysdeps/gnu -I../sysdeps/unix/inet -I../sysdeps/unix/sysv
-I../sysdeps/unix/x86_64 -I../sysdeps/unix -I../sysdeps/posix
-I../sysdeps/x86_64/64 -I../sysdeps/x86_64/fpu/multiarch
-I../sysdeps/x86_64/fpu -I../sysdeps/x86/fpu -I../sysdeps/x86_64/multiarch
-I../sysdeps/x86_64 -I../sysdeps/x86/include -I../sysdeps/x86
-I../sysdeps/ieee754/float128 -I../sysdeps/ieee754/ldbl-96/include
-I../sysdeps/ieee754/ldbl-96 -I../sysdeps/ieee754/dbl-64
-I../sysdeps/ieee754/flt-32 -I../sysdeps/wordsize-64 -I../sysdeps/ieee754
-I../sysdeps/generic -I.. -I../libio -I. -nostdinc -isystem
/usr/lib/gcc/x86_64-linux-gnu/10.3.1/include -isystem /usr/include
-D_LIBC_REENTRANT -include
/home/abuild/rpmbuild/BUILD/glibc-2.34/build-x86_64-openEuler-linux/libc-modules.h
-DMODULE_NAME=nscd -include ../include/libc-symbols.h -DPIC
-DTOP_NAMESPACE=glibc -o
/home/abuild/rpmbuild/BUILD/glibc-2.34/build-x86_64-openEuler-linux/nscd/pwdcache.o
-MD -MP -MF
/home/abuild/rpmbuild/BUILD/glibc-2.34/build-x86_64-openEuler-linux/nscd/pwdcache.o.dt
-MT
/home/abuild/rpmbuild/BUILD/glibc-2.34/build-x86_64-openEuler-linux/nscd/pwdcache.o
We found that -D_FORTIFY_SOURCE=2 is missing, won't removing
-D_FORTIFY_SOURCE=2 for nscd module introduce security issues?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-08-25 2:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 13:52 [Bug nscd/30795] New: " zhanghao383 at huawei dot com
2023-08-24 15:01 ` [Bug nscd/30795] " sam at gentoo dot org
2023-08-25 2:29 ` zhanghao383 at huawei dot com
2023-08-25 2:36 ` zhanghao383 at huawei dot com [this message]
2023-08-25 2:51 ` zhanghao383 at huawei dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-30795-131-j8JvdDnz2C@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).