security - How long should I wait to publicize a vulnerability in a free/open source project? -
in review of free package distributed under apache license found number of bugs ranging obscure code issues security holes.
i've taken following steps:
- i notified project lead through private email 2 weeks ago, , other acknowledgment of said emails, haven't seen any internal or external activity regarding issues raised.
- i've followed policies laid out sans , wiretrip.
questions
- should follow email?
- if no response, should go ahead , post these issues publicly?
- does has been through (from either side) have suggestions how handle this?
truthfully have no obligation either way if:
- you found problems under legitimate installation of software (following tos/fair usage guidelines, etc)
- you did not modify or compromise security of system in known way purposefully setting system in such way insecure (i.e. purposefully uninstalling security measures has)
- you cannot conceivably considered rival financial gain in same market space.
if product purely open source , under free license, last true, leaving first 2 considered (if has commercial licensing may different matter).
you can openly document issues have software long provide opinion, , said issues proof (preferably verified third-party) in form (blog, mailing list, etc).
if security researcher assigned research product, or intending publish findings part of corporate reporting, legal department have additional rules need follow (consult them).
i believe dilema purely ethical , quote 1 part of post:
i have selfish reasons saying "look how clever am! found these problems in code!" tempered wanting give developers time fix code , know ego , pride can involved in these matters.
if consider ethical reasoning fair should follow whatever common sense find reasonable (i believe sans fair in case).
Comments
Post a Comment