carnil wrote:
> Information on CVE-2018-16301 seem to indicate that it first was
> thought to be an issue in tcpdump, but then it's clearly stated that it
> is fixed in libpcap.
> The CVE description submitted to MITRE is as well inline with that:
(okay, but don't use that as aut
Beuc wrote:
> I'm part of the Debian Long Term Support team, and I'd like to assess
> if our packaged versions of libpcap are affected by CVE-2018-16301.
Yes.
> 81c4e00e says it relates to "errors in pcapng reading", but I cannot
> identify the related commit.
> In addition,
