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
JPMorgan Hack: 2FA MIA In Breached Server
Newest First  |  Oldest First  |  Threaded View
<<   <   Page 2 / 2
Technocrati
Technocrati,
User Rank: Ninja
12/27/2014 | 8:56:32 PM
Re: So what?

"... Some of these attacks are exaggerated by news channels and social media."

 

@Dr, T     I agree.  A lot of these attacks are misunderstood banter on the Net.   But what really annoys me is that Chase apparently sat on this information for a long time.   Considering they should have released this news as soon as they were aware.   Enough with how the public is going to perceive you.  

I for one already know Chase is using "smoke and mirrors" when it comes to security.   They are doing no more than is required by law, and that apparently isn't enough.

So why did it take them so long to release this information ?   Only the nieve amongst us really believes Chase or any Net facing business is ever safe from a breech.

If Chase thinks we the public would think less of them because of this, well it has long since been too late for that.

Dr.T
Dr.T,
User Rank: Ninja
12/27/2014 | 8:49:25 AM
Re: The Real Issue of Data Breech and J.P. Morgan
I agree. This is the main problem. Attacks keep happening, we keep reporting but nothing happens to attackers and the ones who are responsible for allowing that. That is the biggest and most important loophole in security.
Dr.T
Dr.T,
User Rank: Ninja
12/27/2014 | 8:46:30 AM
Re: J.P Morgan: Because We Said So.........
It may simply mean sensitive information such as account number, SSN and balance are kept in the rest of the severs but it is hard to believe those 90 servers do not have PII.
Dr.T
Dr.T,
User Rank: Ninja
12/27/2014 | 8:43:54 AM
Re: J.P. Morgan and The Big Hole
I agree. You can actually put two-factor on servers to decrease risk of exploits, but that being the solution for their hack is that realistic.
Dr.T
Dr.T,
User Rank: Ninja
12/27/2014 | 8:41:11 AM
So what?
80 million businesses email and address and phones are stolen? They did not have to steal that, we could have given them this induration. Some of these attacks are exaggerated by news channels and social media. Two factor authentication is not a solution for security problems, especially for JPMorgan.
Technocrati
Technocrati,
User Rank: Ninja
12/24/2014 | 8:58:25 PM
The Real Issue of Data Breech and J.P. Morgan

Just what is Chase doing for those millions of customers whose data was compromised ?  (and an uncomfortable silence ensues).

 

I think I will just keep asking until I get an answer.  

Technocrati
Technocrati,
User Rank: Ninja
12/24/2014 | 8:53:21 PM
J.P Morgan: Because We Said So.........

"...The JPMorgan hackers were able to access more than 90 of the bank's servers, but were detected before they got to sensitive customer financial information."

 

Chase really expects the public to believe this ?    Of course they do - they are Chase after all.   This is literally amazing, I believe the word is ludicrous.

Technocrati
Technocrati,
User Rank: Ninja
12/24/2014 | 8:49:25 PM
J.P. Morgan and The Big Hole

"....the big hole that led attackers to the data was the lack of two-factor authentication of one of the bank's network servers."

 

What can you say about this ?   Seriously two-factor authentication ?!    This is simply blantant carelessness by admins and the Bank itself.  I am not about to let Chase off the hook for this in it's entirety, but looking at it from a micro-level it is clear ( to me at least) that someone was asleep at the wheel.  Taking their job for granted maybe ?  

Whatever the case, it does not speak well of Chase ( I am not sure anything could actually) nor does it speak well of their IT department.

I wonder if this is the same (IT) group that handles high frequency trading and the rest ?   If not get them on this issue - they have a proven track record of success.

<<   <   Page 2 / 2


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
The Promise and Reality of Cloud Security
Cloud security has been part of the cybersecurity conversation for years but has been on the sidelines for most enterprises. The shift to remote work during the COVID-19 pandemic and digital transformation projects have moved cloud infrastructure front-and-center as enterprises address the associated security risks. This report - a compilation of cutting-edge Black Hat research, in-depth Omdia analysis, and comprehensive Dark Reading reporting - explores how cloud security is rapidly evolving.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2023-25012
PUBLISHED: 2023-02-02
The Linux kernel through 6.1.9 has a Use-After-Free in bigben_remove in drivers/hid/hid-bigbenff.c via a crafted USB device because the LED controllers remain registered for too long.
CVE-2022-37034
PUBLISHED: 2023-02-01
In dotCMS 5.x-22.06, it is possible to call the TempResource multiple times, each time requesting the dotCMS server to download a large file. If done repeatedly, this will result in Tomcat request-thread exhaustion and ultimately a denial of any other requests.
CVE-2023-0599
PUBLISHED: 2023-02-01
Rapid7 Metasploit Pro versions 4.21.2 and lower suffer from a stored cross site scripting vulnerability, due to a lack of JavaScript request string sanitization. Using this vulnerability, an authenticated attacker can execute arbitrary HTML and script code in the target browser against another Metas...
CVE-2023-23750
PUBLISHED: 2023-02-01
An issue was discovered in Joomla! 4.0.0 through 4.2.6. A missing token check causes a CSRF vulnerability in the handling of post-installation messages.
CVE-2023-23751
PUBLISHED: 2023-02-01
An issue was discovered in Joomla! 4.0.0 through 4.2.4. A missing ACL check allows non super-admin users to access com_actionlogs.