Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Comments
Vuln Disclosure: Why Security Vendors & Researchers Dont Trust Each Other
Newest First  |  Oldest First  |  Threaded View
Joe Stanganelli
Joe Stanganelli,
User Rank: Ninja
3/31/2016 | 11:18:22 AM
So much for cooperation in security
Reminds me of when Google engineer Tavis Ormandy released a zero-day Microsoft vulnerability before Microsoft had the opportunity to patch it -- and the stark contrast that action and Google's nonchalant response to it bore to the Microsoft Vulnerability Research program.
cjnonsense
cjnonsense,
User Rank: Apprentice
3/24/2016 | 10:01:06 AM
Order of steps
I was very taken by the 'good sense' communicated in this article. My only comment is that for this 5 step approach to really work, the 'BE' steps must come first. In other words, each side must BE trustworthy and each side must BE transparent. Otherwise, the other three steps will never happen.

The root to all of this is humility. If you've lived in any facet of IT for any length of time, you should realize that you cannot and will not ever know it all! It is an impossible task. Openly admitting that to yourself and verbalizing that to anyone else will lead to both trustworthiness and transparency.

The remaining steps could be summarized as seek first to understand and then seek to be understood. Of course, these things all run counter to our natural sense of self protection. Particularly, the protection of our ego(s).

As is so often the case, we are our own worst enemies.


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Black Hat USA 2022 Attendee Report
Black Hat attendees are not sleeping well. Between concerns about attacks against cloud services, ransomware, and the growing risks to the global supply chain, these security pros have a lot to be worried about. Read our 2022 report to hear what they're concerned about now.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-42750
PUBLISHED: 2022-08-12
A cross-site scripting (XSS) vulnerability in Rule Engine in ThingsBoard 3.3.1 allows remote attackers (with administrative access) to inject arbitrary JavaScript within the title of a rule node.
CVE-2021-42751
PUBLISHED: 2022-08-12
A cross-site scripting (XSS) vulnerability in Rule Engine in ThingsBoard 3.3.1 allows remote attackers (with administrative access) to inject arbitrary JavaScript within the description of a rule node.
CVE-2022-35585
PUBLISHED: 2022-08-12
A stored cross-site scripting (XSS) issue in the ForkCMS version 5.9.3 allows remote attackers to inject JavaScript via the "start_date" Parameter
CVE-2022-35587
PUBLISHED: 2022-08-12
A cross-site scripting (XSS) issue in the Fork version 5.9.3 allows remote attackers to inject JavaScript via the "publish_on_date" Parameter
CVE-2022-35589
PUBLISHED: 2022-08-12
A cross-site scripting (XSS) issue in the Fork version 5.9.3 allows remote attackers to inject JavaScript via the "publish_on_time" Parameter.