mailing list archives
Re: Isearch insecure temporary files
From: Kurt Seifried <kseifried () redhat com>
Date: Sun, 30 Dec 2012 17:12:02 -0700
-----BEGIN PGP SIGNED MESSAGE-----
On 12/30/2012 09:16 AM, Henri Salo wrote:
On Sat, Dec 29, 2012 at 08:53:42PM -0700, Kurt Seifried wrote:
One random thought, might it be worth adding structured data to
CVE that basically says when the issue was made public/reported
to the upstream and when upstream 1) acknowledged it (if ever)
and then they patched it (if ever) and when they shipped a fixed
version (if ever). Obviously then you could simply parse for the
time between date reported and date acknowledged/patched/fixed
and see how healthy/responsive the upstream is.
Yes, that would be really useful data with CVEs. OSVDB is
collecting that already. That is not easy task btw.
- Henri Salo
Maybe iDefense or iSIGHT would be willing to share (I know the data
exists, I helped collect it for 9.5 years =). One thing I'm really
noticing as a good rule of thumb:
1) if a project has security@ or similar email and responds timely,
this is good.
2) if a project has security@ or similar email and never responds then
they tend to fix things but not overly quickly/consistently
3) if a project has no security@ or similar email chances are they
don't handle security issues very gracefully (big surprise hey).
Basically if the first result in Google for "report security issue to
X" isn't useful chances are it's not going to end well. The best part
is not all vendors provide a secure means to submit vulnerabilities
(e.g. please provide a PGP encryption key for email, and if you use a
web form please use HTTPS!).
Kurt Seifried Red Hat Security Response Team (SRT)
PGP: 0x5E267993 A90B F995 7350 148F 66BF 7554 160D 4553 5E26 7993
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
-----END PGP SIGNATURE-----