* How to find the original code that causes a CVE?
@ 2021-03-25 20:35 Peng Yu
2021-03-25 20:46 ` tomas
0 siblings, 1 reply; 2+ messages in thread
From: Peng Yu @ 2021-03-25 20:35 UTC (permalink / raw)
To: libc-help
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: How to find the original code that causes a CVE?
2021-03-25 20:35 How to find the original code that causes a CVE? Peng Yu
@ 2021-03-25 20:46 ` tomas
0 siblings, 0 replies; 2+ messages in thread
From: tomas @ 2021-03-25 20:46 UTC (permalink / raw)
To: Peng Yu; +Cc: libc-help
[-- Attachment #1: Type: text/plain, Size: 444 bytes --]
On Thu, Mar 25, 2021 at 03:35:33PM -0500, Peng Yu via Libc-help wrote:
> 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?
You can look it up in the glibc bug database:
https://sourceware.org/bugzilla/show_bug.cgi?id=CVE-2017-16997
Cheers
-- tomas
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-03-25 20:46 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-03-25 20:35 How to find the original code that causes a CVE? Peng Yu
2021-03-25 20:46 ` tomas
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).