[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <512E6279.3050003@fifthhorseman.net>
Date: Wed, 27 Feb 2013 11:46:01 -0800
From: Daniel Kahn Gillmor <dkg@...thhorseman.net>
To: oss-security@...ts.openwall.com
CC: "Jason A. Donenfeld" <Jason@...c4.com>
Subject: Re: CVE request - Linux kernel: VFAT slab-based buffer
overflow
On 02/27/2013 11:26 AM, Jason A. Donenfeld wrote:
> "If you see something, say something."
I'd love it if it were this simple, but it's not. It's work. Look at
the examples of good security reports on this list (e.g. ones that were
issued CVEs with no extra discussion needed).
These reports require thoughtful analysis, testing, and a good sense of
what the tradeoffs are for making the fixes. this takes time (and
skill). Sometimes all the work and analysis leads to a conclusion that
the failure was not actually exploitable in any significant way. And
not every fix has obvious security implications -- some only become
apparent after the investigative work is done.
Some fixes are simple, fixing them has no obvious side effects, and
there is clear evidence not fixing it could lead to an exploit. You
could even argue that the issue that started this thread is one of them
(though i haven't spent enough time to understand it well enough to know
if that's the case).
If *every* bug fix were reported to oss-security without this work, as
something like "i'm not sure, but this might be security-related", then
this list would drown in noise (the NYC MTA's supposed anti-terrorism
campaign suffers this same flaw, btw).
So, we have a culture of asking people to report security flaws only
after doing some level of work to ensure that the report is correct and
understood.
We have to acknowledge that this is extra work, and not everyone has the
time (or skill) to do it properly.
--dkg
Download attachment "signature.asc" of type "application/pgp-signature" (1028 bytes)
Powered by blists - more mailing lists
Please check out the
Open Source Software Security Wiki, which is counterpart to this
mailing list.
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
