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/27/2014 | 8:56:32 PM
"... 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.