Vulnerabilities / Threats

7/25/2017
07:30 AM
50%
50%

Regulators Question Wells Fargo Regarding Data Breach

Scrutiny a result of a lawyer's unauthorized release of sensitive information on tens of thousands of wealthy Well Fargo customers.

Wells Fargo again finds itself embroiled in controversy after an attorney releases the names, social security numbers, and account balances for 50,000 of the institution's wealthier customers, according to a report in Bloomberg.

The Financial Industry Regulatory Authority has contacted at least one attorney to learn more about the mishap, how it occurred, and why Wells Fargo did not detect the snafu, the report notes. The data breach occurred when an attorney representing Wells Fargo sent the sensitive documents to another attorney who was representing a client who was suing a managing director of the bank.

When the sensitive documents were sent, it was done without a confidentiality agreement between the parties or a protective order, Bloomberg reports. The plaintiff in the case, Gary Sinderbrand, a former Wells Fargo Advisors managing director, is suing Steven Sinderbfrand, his brother and also a Wells Fargo managing director, over allegations he is owed approximately $870,000 in unpaid consulting fees.

Read more about the Wells Fargo breach 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
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
7/26/2017 | 10:33:48 AM
Re: incredible
"if this is confirmed, this is big news !"

Agree with this, nobody wants bank information will be out in the public.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
7/26/2017 | 10:32:45 AM
Attorney to attorney
 

"an attorney representing Wells Fargo sent the sensitive documents to another attorney who was representing a client"

If it just ends there I would not think this will be any big issue, attorneys share data all the times. Better be in a secure way.

 
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
7/26/2017 | 10:30:28 AM
Wells Fargo Breach?
I have not heard this one, why there is no noise on this, this may be important to many people.
jeandarmouni
50%
50%
jeandarmouni,
User Rank: Apprentice
7/25/2017 | 4:08:08 PM
incredible
if this is confirmed, this is big news !
Government Shutdown Brings Certificate Lapse Woes
Curtis Franklin Jr., Senior Editor at Dark Reading,  1/11/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
The Year in Security 2018
This Dark Reading Tech Digest explores the biggest news stories of 2018 that shaped the cybersecurity landscape.
Flash Poll
How Enterprises Are Attacking the Cybersecurity Problem
How Enterprises Are Attacking the Cybersecurity Problem
Data breach fears and the need to comply with regulations such as GDPR are two major drivers increased spending on security products and technologies. But other factors are contributing to the trend as well. Find out more about how enterprises are attacking the cybersecurity problem by reading our report today.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-6443
PUBLISHED: 2019-01-16
An issue was discovered in NTPsec before 1.1.3. Because of a bug in ctl_getitem, there is a stack-based buffer over-read in read_sysvars in ntp_control.c in ntpd.
CVE-2019-6444
PUBLISHED: 2019-01-16
An issue was discovered in NTPsec before 1.1.3. process_control() in ntp_control.c has a stack-based buffer over-read because attacker-controlled data is dereferenced by ntohl() in ntpd.
CVE-2019-6445
PUBLISHED: 2019-01-16
An issue was discovered in NTPsec before 1.1.3. An authenticated attacker can cause a NULL pointer dereference and ntpd crash in ntp_control.c, related to ctl_getitem.
CVE-2019-6446
PUBLISHED: 2019-01-16
An issue was discovered in NumPy 1.16.0 and earlier. It uses the pickle Python module unsafely, which allows remote attackers to execute arbitrary code via a crafted serialized object, as demonstrated by a numpy.load call.
CVE-2019-6442
PUBLISHED: 2019-01-16
An issue was discovered in NTPsec before 1.1.3. An authenticated attacker can write one byte out of bounds in ntpd via a malformed config request, related to config_remotely in ntp_config.c, yyparse in ntp_parser.tab.c, and yyerror in ntp_parser.y.