From: Peng Yu <pengyu.ut@gmail.com>
To: libc-help <libc-help@sourceware.org>
Subject: How to find the original code that causes a CVE?
Date: Thu, 25 Mar 2021 15:35:33 -0500 [thread overview]
Message-ID: <CABrM6wmvZivW6sF2zNwY_BizSaqXf_ECFisAqFtgVoZUxa=5UA@mail.gmail.com> (raw)
Hi,
https://www.cvedetails.com/cve/CVE-2017-16997/
I see this CVE for glibc. But it is not clear how to look up which
line of the source code causes this vulnerability. Could anybody show
me how to look this up?
--
Regards,
Peng
next reply other threads:[~2021-03-25 20:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 20:35 Peng Yu [this message]
2021-03-25 20:46 ` tomas
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='CABrM6wmvZivW6sF2zNwY_BizSaqXf_ECFisAqFtgVoZUxa=5UA@mail.gmail.com' \
--to=pengyu.ut@gmail.com \
--cc=libc-help@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).