If a tree falls in the woods…

[This was originally published on the OSVDB blog.]

If a researcher discloses a vulnerability only to VDBs, and some/all of them publish the information, was the vulnerability really disclosed? Yes, of course, but should it have been? Are VDBs responsible for the information? Does it fall on us to check every thing we get and verify the vendor received it first? Snap answer is ‘yes’, but if so, is the answer the same with information published on a mail list? Snap answer is ‘no’.

This creates a situation where VDBs are held to certain standards for responsible disclosure, and are virtually forced to play middle man between the vendor and researcher. VDBs are forced to take on a role they may not have intended to, or take a hit in their reputation for being responsible with information that may put others at risk.

Late night babbling, or is that a shitty deal for VDBs?

Fiasco: BlackHat, Cisco, ISS, Lynn

[This was originally published on the OSVDB blog.]

There are far too many articles covering this topic to justify me rewriting the story in my own words. So in summary, relevant links with background. End up with Schneier’s commentary for a good summary and additional links.

BlackHat Briefings: Cisco IOS Security Architecture by Michael Lynn

Security researcher quits job and blows whistle on Cisco’s fatal flaws

Cisco, ISS file suit against rogue researcher

Cisco Security Hole a Whopper

Cisco Security Advisory: IPv6 Crafted Packet Vulnerability

Cisco, ISS, Michael Lynn and Black Hat sign legal accord
Cisco settles dispute with flaw researcher

Text of the Cisco-ISS-Lynn-Black Hat Agreement

Rick Forno hosts Lynn PDF, gets C&D from ISS

Cisco Harasses Security Researcher