From owner-freebsd-ports@freebsd.org Mon Oct 9 20:35:00 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A5934E3B316 for ; Mon, 9 Oct 2017 20:35:00 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 887217E85D; Mon, 9 Oct 2017 20:35:00 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1354) id DA1852716; Mon, 9 Oct 2017 20:34:59 +0000 (UTC) From: Jan Beich To: Matthew Seaman Cc: freebsd-ports@freebsd.org Subject: Re: New pkg audit FNs References: Date: Mon, 09 Oct 2017 22:34:56 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Oct 2017 20:35:00 -0000 Matthew Seaman writes: > On 09/10/2017 16:57, Roger Marquis wrote: > >> The reason I ask is CVE-2017-12617 was announced almost a week ago yet >> there's no mention of it in the vulnerability database=C2=A0 The tomcat8 >> port's Makefile also still points to the older, vulnerable version. >> Tomcat is one of those popular, internet-facing applications that sites >> need to check and/or update quickly when CVEs are released and most >> admins probably don't expect "pkg audit" to throw false negatives. > > Ports-secteam (and secteam, for that matter) will update VuXML when they > know about vulnerabilities that affect FreeBSD ports, however the usual > mechanism is that the port maintainer either updates VuXML themselves > directly or tells the appropriate people that there are vulnerabilities > that need to be recorded. What happened to querying CVE database using CPE strings? ENOTIME is a common disease in volunteer projects, ports-secteam@ is no exception. Finding missing entries is trivial if one looks at Debian tracker. Let's pick something popular e.g., tiff-4.0.8 has 6 CVEs none of which are fixed in the port. https://wiki.freebsd.org/Ports/CPE