Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2023-25015PUBLISHED: 2023-02-02Clockwork Web before 0.1.2, when Rails before 5.2 is used, allows CSRF.
CVE-2023-25013PUBLISHED: 2023-02-02An issue was discovered in the femanager extension before 5.5.3, 6.x before 6.3.4, and 7.x before 7.1.0 for TYPO3. Missing access checks in the InvitationController allow an unauthenticated user to set the password of all frontend users.
CVE-2023-25014PUBLISHED: 2023-02-02An issue was discovered in the femanager extension before 5.5.3, 6.x before 6.3.4, and 7.x before 7.1.0 for TYPO3. Missing access checks in the InvitationController allow an unauthenticated user to delete all frontend users.
CVE-2023-25012PUBLISHED: 2023-02-02The 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-37034PUBLISHED: 2023-02-01In 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.
User Rank: Ninja
9/9/2014 | 10:48:07 AM
If there were anything to add, specifically in the US, it would be state laws or regulations.
More and more I am running into situations where states have established statutory requirements for the protection and handling of specific categories of data that may exceed or augments some of the regulatory directives you listed.
So many fingers in the regulatory security jar.
Not complaining... any regulatory requirement from any angle helps in the effort to gain resources and support for security controls that are necessary. But the complexity of bringing all of the requirements together and addressed accordingly can be daunting at times.