Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-26333PUBLISHED: 2021-09-21An information disclosure vulnerability exists in AMD Platform Security Processor (PSP) chipset driver. The discretionary access control list (DACL) may allow low privileged users to open a handle and send requests to the driver resulting in a potential data leak from uninitialized physical pages.
CVE-2021-31917PUBLISHED: 2021-09-21
A flaw was found in Red Hat DataGrid 8.x (8.0.0, 8.0.1, 8.1.0 and 8.1.1) and Infinispan (10.0.0 through 12.0.0). An attacker could bypass authentication on all REST endpoints when DIGEST is used as the authentication method. The highest threat from this vulnerability is to data confidentiality and i...
CVE-2021-20829PUBLISHED: 2021-09-21Cross-site scripting vulnerability due to the inadequate tag sanitization in GROWI versions v4.2.19 and earlier allows remote attackers to execute an arbitrary script on the web browser of the user who accesses a specially crafted page.
CVE-2021-20037PUBLISHED: 2021-09-21SonicWall Global VPN Client 4.10.5 installer (32-bit and 64-bit) incorrect default file permission vulnerability leads to privilege escalation which potentially allows command execution in the host operating system. This vulnerability impacts GVC 4.10.5 installer and earlier.
CVE-2021-39229PUBLISHED: 2021-09-20
Apprise is an open source library which allows you to send a notification to almost all of the most popular notification services available. In affected versions users who use Apprise granting them access to the IFTTT plugin (which just comes out of the box) are subject to a denial of service attack...
Enterprise Cybersecurity Plans in a Post-Pandemic WorldDownload the Enterprise Cybersecurity Plans in a Post-Pandemic World report to understand how security leaders are maintaining pace with pandemic-related challenges, and where there is room for improvement.
Incident Readiness and Building Response Playbook
In this special report, learn the Xs and Os of any good security incident readiness and response playbook.
Tweet This
0 Comments
User Rank: Ninja
8/20/2020 | 5:19:39 PM
I am not sure if I agree with this reasoning, there is a thing called Zero-Trust especially for environments like hospitals, police stations, utility companies, and IT companies who should have these devices in an isolated environment or VLAN (VXLAN in some cases - VMware Centric). If configured properly, you only allow specific devices to communicate with those devices over a secured connection. I think IPv6 is good to secure devices like this (IoT Devices) because they add an additional layer to the network (IPv6 AES256 IPSec ESP/AH Tunnels). The writer stated that the user should have strong NAC (I agree) with tools to limit the execution of executables on the network so it limits ransomware and external threats and attacks.
This is an example but it gives the reader an idea of the various devices that could exist in any sort of environment. We need to start thinking of Zero-trust designs using locked down methods where baselines of servers and IoT devices are segmented with only a few devices to communicate with servers and/or telecom/network devices.
But think about this, if I can modify the settings on a PLC device, then I can change water temperature, heating/cooling, electrical regulation, so that means those devices need to be isolated because their security posture will not be as high as those in Zone 0 or 1.
So to me, it is not only about the importance of the device, but where the device is located in the IT ecosystem and its function. There needs to be a conversation so if there is any doubt in your mind, then you may need to fortify the design of the network with MFA/2FA, limit who has access to certain devices, if there is a need, put them on a VLAN where VLANs from the admin staff is part of the multi-connect VLAN or VXLAN, and finally, the vendor needs to be consulted to share with them any shortcomings you find (Continuous Diagnostic and Mitigation - CDM).
T