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
Google Paid Over $1.5 Million In Bug Bounties In 2014
Newest First  |  Oldest First  |  Threaded View
Joe Stanganelli
Joe Stanganelli,
User Rank: Ninja
2/5/2015 | 7:10:57 PM
Re: Google so great?
@Marilyn: Indeed.  On the other hand, there is computer science research that indicates that a software project can only have a maximum number of "useful" reviewers -- typically between two and four -- before slamming into a brick wall of diminishing returns.  So, to play devil's advocate with myself, maybe that $1.5 mil. on the front end would have been a waste.

The other problem is that security review is less exciting and interesting than feature review -- a more significant problem that could use a solution.
Marilyn Cohodas
Marilyn Cohodas,
User Rank: Strategist
2/3/2015 | 8:47:25 AM
Re: Google so great?
There is definitely more that can always be done in browser application security (and elsewhere). I wonder how far Google's $1.5 million payout  in bug bounties would have gone on the front end  versus the back end of the process...
Joe Stanganelli
Joe Stanganelli,
User Rank: Ninja
1/31/2015 | 9:30:43 PM
Re: Google so great?
Oh, don't geet me wrong.  I applaud Google's bug bounty program.  Collaboration is key in cybersecurity.  Nonetheless, with the sheer amount of bugs being found and bug bounties being paid out here, it strongly suggests that Google's engineers aren't quite pulling their security weight.
RyanSepe
RyanSepe,
User Rank: Ninja
1/31/2015 | 12:37:57 PM
Re: Google so great?
I would prefer that the incentive program be the case because not even the Google Engineers can anticipate everything. Having your product tested by a larger group will ensure that more vectors are tested. With technology increasing its capabilities quickly, its not like Google has a finite checklist that they can run through every time. The bug possiblities change with the type of software.
Joe Stanganelli
Joe Stanganelli,
User Rank: Ninja
1/30/2015 | 10:46:49 PM
Google so great?
Maybe this is just the cynic in me, but at a certain point, with all of these bug bounties being paid out, one has to question the quality of the hiring and/or corporate culture at Google.


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
Creating an Effective Incident Response Plan
Security teams are realizing their organizations will experience a cyber incident at some point. An effective incident response plan that takes into account their specific requirements and has been tested is critical. This issue of Tech Insights also includes: -a look at the newly signed cyber-incident law, -how organizations can apply behavioral psychology to incident response, -and an overview of the Open Cybersecurity Schema Framework.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-43705
PUBLISHED: 2022-11-27
In Botan before 2.19.3, it is possible to forge OCSP responses due to a certificate verification error. This issue was introduced in Botan 1.11.34 (November 2016).
CVE-2022-45934
PUBLISHED: 2022-11-27
An issue was discovered in the Linux kernel through 6.0.10. l2cap_config_req in net/bluetooth/l2cap_core.c has an integer wraparound via L2CAP_CONF_REQ packets.
CVE-2022-45931
PUBLISHED: 2022-11-27
A SQL injection issue was discovered in AAA in OpenDaylight (ODL) before 0.16.5. The aaa-idm-store-h2/src/main/java/org/opendaylight/aaa/datastore/h2/UserStore.java deleteUser function is affected when the API interface /auth/v1/users/ is used.
CVE-2022-45932
PUBLISHED: 2022-11-27
A SQL injection issue was discovered in AAA in OpenDaylight (ODL) before 0.16.5. The aaa-idm-store-h2/src/main/java/org/opendaylight/aaa/datastore/h2/RoleStore.java deleteRole function is affected when the API interface /auth/v1/roles/ is used.
CVE-2022-45933
PUBLISHED: 2022-11-27
KubeView through 0.1.31 allows attackers to obtain control of a Kubernetes cluster because api/scrape/kube-system does not require authentication, and retrieves certificate files that can be used for authentication as kube-admin. NOTE: the vendor's position is that KubeView was a "fun side proj...