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
GitHub Named in Capital One Breach Lawsuit
Newest First  |  Oldest First  |  Threaded View
tdsan
tdsan,
User Rank: Ninja
8/14/2019 | 3:56:57 PM
Wow, then they need to involve Google, MS, Apple and AWS as well

The lawsuit, filed in US District Court for the Northern District of California, claims that GitHub (now owned by Microsoft) "actively encourages" hackers,  and that this active encouragement means that it has a higher responsibility than most repositories to scan uploaded files for dangerous or illicit data.

This lawsuit is almost laughable, anything that is deemed positive can be turned negative. Github is a repository for developers to come up with code and sharing that code with other organizations to address problems in the wild, I think this is more of a company trying to divert blame as opposed to facing the facts and being accountable for their actions. This says alot about CapitalOne - the organization - who has been blindsided by someone whom they dealt with in the recent past; but it also sheds light on their lack of oversight and attention to detail (this says a lot about the organization as a whole).

I am looking forward to hearing more about the lawsuit and interested in hearing what the judge says in the hearing, this should be interesting.

T

 


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-1813
PUBLISHED: 2022-05-22
OS Command Injection in GitHub repository yogeshojha/rengine prior to 1.2.0.
CVE-2022-1809
PUBLISHED: 2022-05-21
Access of Uninitialized Pointer in GitHub repository radareorg/radare2 prior to 5.7.0.
CVE-2022-31267
PUBLISHED: 2022-05-21
Gitblit 1.9.2 allows privilege escalation via the Config User Service: a control character can be placed in a profile data field, such as an emailAddress%3Atext '[email protected]\n\trole = "#admin"' value.
CVE-2022-31268
PUBLISHED: 2022-05-21
A Path Traversal vulnerability in Gitblit 1.9.3 can lead to reading website files via /resources//../ (e.g., followed by a WEB-INF or META-INF pathname).
CVE-2022-31264
PUBLISHED: 2022-05-21
Solana solana_rbpf before 0.2.29 has an addition integer overflow via invalid ELF program headers. elf.rs has a panic via a malformed eBPF program.