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.

Attacks/Breaches

8/14/2019
12:30 PM
50%
50%

GitHub Named in Capital One Breach Lawsuit

A new lawsuit says that GitHub bears responsibility for the Capital One breach because it actively encourages hacking and stored stolen data.

The fallout from the Capital One data breach continues, with a recent class-action lawsuit naming the financial giant — and GitHub, the online data repository that has become central to many companies' agile and devops coding efforts.

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.

According to the lawsuit, files containing information on the methods used in the breach were uploaded to the site in April, but not removed until July, when GitHub was alerted by Capital One.

In a statement to Dark Reading, GitHub said, "GitHub promptly investigates content, once it's reported to us, and removes anything that violates our Terms of Service. The file posted on GitHub in this incident did not contain any Social Security numbers, bank account information, or any other reportedly stolen personal information. We received a request from Capital One to remove content containing information about the methods used to steal the data, which we took down promptly after receiving their request."

The suit is depending on a standard of "morally culpable," as opposed to "legally culpable," which is a commonly used legal standard. 

For more, read here and here.

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
ebyjeeby
50%
50%
ebyjeeby,
User Rank: Strategist
8/20/2019 | 12:52:31 PM
Re: What's in your repository?
That's funny!
kratiw
50%
50%
kratiw,
User Rank: Strategist
8/16/2019 | 2:25:28 PM
What's in your repository?
Sorry, I had to do it.
tdsan
50%
50%
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

 
The Cold Truth about Cyber Insurance
Chris Kennedy, CISO & VP Customer Success, AttackIQ,  11/7/2019
Why Cyber-Risk Is a C-Suite Issue
Marc Wilczek, Digital Strategist & CIO Advisor,  11/12/2019
6 Small-Business Password Managers
Curtis Franklin Jr., Senior Editor at Dark Reading,  11/8/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-16863
PUBLISHED: 2019-11-14
STMicroelectronics ST33TPHF2ESPI TPM devices before 2019-09-12 allow attackers to extract the ECDSA private key via a side-channel timing attack because ECDSA scalar multiplication is mishandled, aka TPM-FAIL.
CVE-2019-18949
PUBLISHED: 2019-11-14
SnowHaze before 2.6.6 is sometimes too late to honor a per-site JavaScript blocking setting, which leads to unintended JavaScript execution via a chain of webpage redirections targeted to the user's browser configuration.
CVE-2011-1930
PUBLISHED: 2019-11-14
In klibc 1.5.20 and 1.5.21, the DHCP options written by ipconfig to /tmp/net-$DEVICE.conf are not properly escaped. This may allow a remote attacker to send a specially crafted DHCP reply which could execute arbitrary code with the privileges of any process which sources DHCP options.
CVE-2011-1145
PUBLISHED: 2019-11-14
The SQLDriverConnect() function in unixODBC before 2.2.14p2 have a possible buffer overflow condition when specifying a large value for SAVEFILE parameter in the connection string.
CVE-2011-1488
PUBLISHED: 2019-11-14
A memory leak in rsyslog before 5.7.6 was found in the way deamon processed log messages are logged when $RepeatedMsgReduction was enabled. A local attacker could use this flaw to cause a denial of the rsyslogd daemon service by crashing the service via a sequence of repeated log messages sent withi...