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
Diverse White Hat Community Leads To Diverse Vuln Disclosures
Newest First  |  Oldest First  |  Threaded View
Marilyn Cohodas
Marilyn Cohodas,
User Rank: Strategist
1/26/2015 | 9:40:26 AM
Re: Alas...
The key to the success of these bug-bounty programs relies on the credibility and legitimacy of the white-hat hackers. Not sure that a platform like Wooyun is the right model of the U.S. , especially under the existing and possible expansion of the CFAA, as @Joe Stanganelli points out.
Joe Stanganelli
Joe Stanganelli,
User Rank: Ninja
1/25/2015 | 8:04:39 PM
Alas...
Unfortunately, it would seem that if the current administration gets its way (as Jeff Williams wrote for Dark Reading recently), the CFAA will be expanded significantly -- which is harmful to and disincentivizes white-hat hackers and independent bug-hunters because it penalizes their security hole-finding activities.

I recently saw Katie Moussouris, HackerOne's Chief Policy Officer, speak at a cybersecurity conference, and she was insistent on this point, calling hackers "a giant pool of untapped resources" and advising attendees to "be prepared to receive a notification from a friendly hacker[.]"  (In particular, she pointed to the example of Polish hacker group the Last Stage of Delirium (LSOD) IDing the vulnerability that led to the Blaster worm, and Microsoft's response: sending employees to Poland to recruit the hackers.)
Marilyn Cohodas
Marilyn Cohodas,
User Rank: Strategist
1/23/2015 | 1:44:16 PM
Re: Looking for vulnerabilities
I really hope that we can come up with something that serves to protect IT infrastructures while at the same time, not detract from the efforts to assess the same infrastructures we try to protect.


I hope so too, @gonz. I don't have a lot of confidence in our legislators (state or federal) in getting it right. But doing nothing is worse...
GonzSTL
GonzSTL,
User Rank: Ninja
1/23/2015 | 1:11:26 PM
Re: Looking for vulnerabilities
@Sara Peters: The legislation issue is definitely huge, as noted in the recent posts by Ericka Chikowski and Jeff Williams among others, here on Dark Reading. I'm sure several security pros are keenly aware and keeping abreast of the current state of legislations regarding this topic. I really hope that we can come up with something that serves to protect IT infrastructures while at the same time, not detract from the efforts to assess the same infrastructures we try to protect. As I see it, the federal and state legislative environments regarding this issue are quite a mess, with overlapping and conflicting scopes, confusing and unclear laws, etc. I am really surprised that someone has not yet formed an official umbrella group that brings all the players together to hammer out a definitive and comprehensive solution on a national scale. Time is getting uncomfortably short; just look at the recent Sony attack, which I believe to be just a precursor to more sinister and devastating attacks in the future.
Sara Peters
Sara Peters,
User Rank: Author
1/23/2015 | 12:26:51 PM
Re: Looking for vulnerabilities
@GonzSTL  It's a dilemma, but my biggest problem is the huge disparity between how software vulnerability research is legislated and how web vulnerability research is legislated. A lot of security people don't even know that they could get in trouble for the gentlest knock on the door.

The key example for me is Daniel Cuthbert, who was convicted under the Computer Misuse Act several years ago. He had donated money to a tsunami relief charity, then gotten no confirmation page or any indication that his donation had gone through. As a security professional, he started wondering if maybe this was a fraudulent charity set up by cybercriminals. So he did a little shell code command just to see if the site had any security on it (assuming that a legitimate site would).

Then he decided it was probably legit, and thought nothing of it. Until the police came to his office and took him off in handcuffs.
GonzSTL
GonzSTL,
User Rank: Ninja
1/23/2015 | 11:40:46 AM
Looking for vulnerabilities
"... seeking vulnerabilities on another person's website without explicit authorization to do so, is technically a felony under the Computer Fraud and Abuse Act."

This sounds like a huge moral dilemma. It isn't right to be scanning a website just to see if there is a vulnerability in it. I get that. Now if I was the website owner, I would rather have a white hat tell me that there is a vulnerability in my website which was uncovered while "scanning", than find out that the vulnerability was exploited by seeing my customers' PII or PHI or financial data being traded in the black market. How would I feel, though, about someone scanning my website without my permission, just to see if there is a vulnerability? I would not be happy about it at all, but at the same time, I really would like to know if I have a potential problem. I do not think that I would not report it to the authorities as a violation of the CFAA unless they broke the website and I lose revenue as a result. Regardless, I would probably let the white hat know that the action they took wasn't entirely legit ... then thank them for finding it, of course! Almost sounds like a love/hate relationship, doesn't it? I'm sure there are many others who think that way. Any thoughts?


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
Incorporating a Prevention Mindset into Threat Detection and Response
Threat detection and response systems, by definition, are reactive because they have to wait for damage to be done before finding the attack. With a prevention-mindset, security teams can proactively anticipate the attacker's next move, rather than reacting to specific threats or trying to detect the latest techniques in real-time. The report covers areas enterprises should focus on: What positive response looks like. Improving security hygiene. Combining preventive actions with red team efforts.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-31650
PUBLISHED: 2022-05-25
In SoX 14.4.2, there is a floating-point exception in lsx_aiffstartwrite in aiff.c in libsox.a.
CVE-2022-31651
PUBLISHED: 2022-05-25
In SoX 14.4.2, there is an assertion failure in rate_init in rate.c in libsox.a.
CVE-2022-29256
PUBLISHED: 2022-05-25
sharp is an application for Node.js image processing. Prior to version 0.30.5, there is a possible vulnerability in logic that is run only at `npm install` time when installing versions of `sharp` prior to the latest v0.30.5. If an attacker has the ability to set the value of the `PKG_CONFIG_PATH` e...
CVE-2022-26067
PUBLISHED: 2022-05-25
An information disclosure vulnerability exists in the OAS Engine SecureTransferFiles functionality of Open Automation Software OAS Platform V16.00.0112. A specially-crafted series of network requests can lead to arbitrary file read. An attacker can send a sequence of requests to trigger this vulnera...
CVE-2022-26077
PUBLISHED: 2022-05-25
A cleartext transmission of sensitive information vulnerability exists in the OAS Engine configuration communications functionality of Open Automation Software OAS Platform V16.00.0112. A targeted network sniffing attack can lead to a disclosure of sensitive information. An attacker can sniff networ...