Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-2094PUBLISHED: 2023-02-08The Yellow Yard Searchbar WordPress plugin before 2.8.2 does not escape some URL parameters before outputting them back to the user, leading to Reflected Cross-Site Scripting
CVE-2022-43761PUBLISHED: 2023-02-08Missing authentication when creating and managing the B&R APROL database in versions < R 4.2-07 allows reading and changing the system configuration.
CVE-2023-0740PUBLISHED: 2023-02-08Cross-site Scripting (XSS) - Stored in GitHub repository answerdev/answer prior to 1.0.4.
CVE-2023-0741PUBLISHED: 2023-02-08Cross-site Scripting (XSS) - DOM in GitHub repository answerdev/answer prior to 1.0.4.
CVE-2023-0742PUBLISHED: 2023-02-08Cross-site Scripting (XSS) - Stored in GitHub repository answerdev/answer prior to 1.0.4.
User Rank: Ninja
12/24/2014 | 8:49:25 PM
"....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.