We strongly recommend the following industry cybersecurity best practices.
https://www.se.com/us/en/download/document/7EN52-0390/
* Locate control and safety system networks and remote devices behind firewalls and isolate them from the business network.
* Install physical controls so no unauthorized personnel can access your industrial control and safety systems, components, peripheral equipment, and networks.
* Place all controllers in locked cabinets and never leave them in the “Program” mode.
* Never connect programming software to any network other than the network intended for that device.
* Scan all methods of mobile data exchange with the isolated network such as CDs, USB drives, etc. before use in the terminals or any node connected to these networks.
* Never allow mobile devices that have connected to any other network besides the intended network to connect to the safety or control networks without proper sanitation.
* Minimize network exposure for all control system devices and systems and ensure that they are not accessible from the Internet.
* When remote access is required, use secure methods, such as Virtual Private Networks (VPNs). Recognize that VPNs may have vulnerabilities and should be updated to the most current version available. Also, understand that VPNs are only as secure as the connected devices.
For more information refer to the Schneider Electric Recommended Cybersecurity Best Practices document.
Red Hat build of Keycloak is an integrated sign-on solution, available as a Red Hat JBoss Middleware for OpenShift containerized image. The Red Hat build of Keycloak for OpenShift image provides an authentication server that you can use to log in centrally, log out, and register. You can also manage user accounts for web applications, mobile applications, and RESTful web services.
Red Hat build of Keycloak Operator for OpenShift simplifies deployment and management of Keycloak 26.0.6 clusters.
This erratum releases new images for Red Hat build of Keycloak 26.0.6 for use within the OpenShift Container Platform cloud computing Platform-as-a-Service (PaaS) for on-premise or private cloud deployments, aligning with the standalone product release.
Security fixes:
* Sensitive Data Exposure in Keycloak Build Process (CVE-2024-10451)
* Keycloak Denial of Service (CVE-2024-10270)
* Keycloak path trasversal (CVE-2024-10492)
* Keycloak proxy header handling Denial-of-Service (DoS) vulnerability (CVE-2024-9666)
* Keycloak TLS passthrough (CVE-2024-10039)
Red Hat has issued a security advisory for Red Hat build of Keycloak 24.0.5 addressing an exposure of sensitive information in the Pushed Authorization Requests (PAR) KC_RESTART cookie. This vulnerability is tracked as CVE-2024-4540 and is rated with low severity. The advisory recommends updating to the fixed version 24.0.5 to mitigate the issue. Keycloak is a standalone server providing authentication and single sign-on capabilities for web and mobile applications.
CVE-2023-33106 is a high-severity memory corruption vulnerability in Qualcomm Snapdragon platforms caused by an out-of-range pointer offset when submitting a large list of sync points via the IOCTL_KGSL_GPU_AUX_COMMAND interface. This flaw affects a wide range of Snapdragon chipsets used in mobile, wearable, automotive, and IoT devices. Exploitation could lead to full compromise of confidentiality, integrity, and availability without requiring user interaction or privileges. Although no known exploits are currently reported in the wild, the vulnerability's nature and broad impact make it a significant risk. European organizations relying on devices with affected Snapdragon chipsets, especially in critical infrastructure, automotive, and mobile sectors, could face severe operational and data security impacts. Mitigation requires prompt firmware and driver updates from device manufacturers and careful validation of GPU command inputs. Countries with high adoption of Snapdragon-based devices and strong automotive and mobile technology sectors, such as Germany, France, and the UK, are most likely to be impacted.
CVE-2023-33063 is a high-severity use-after-free vulnerability (CWE-416) affecting numerous Qualcomm Snapdragon platforms and related products. It involves memory corruption in DSP Services triggered during remote calls from the High-Level Operating System (HLOS) to the Digital Signal Processor (DSP). The vulnerability requires low privileges and no user interaction but local access, enabling potential attackers to execute arbitrary code or cause denial of service. This flaw impacts confidentiality, integrity, and availability of affected devices. While no known exploits are currently reported in the wild, the broad range of affected Snapdragon platforms, including mobile, IoT, automotive, and wearable devices, poses a significant risk. European organizations relying on Qualcomm Snapdragon-based infrastructure or devices should prioritize patching once updates are available. Mitigation involves applying vendor patches, restricting local access, and monitoring for anomalous DSP service behavior. Countries with high mobile and IoT adoption, such as Germany, France, UK, and the Nordics, are most likely to be affected due to market penetration and strategic technology use. The vulnerability’s CVSS score is 7.8, reflecting its high severity given the potential for remote code execution and system compromise without user interaction.
CVE-2023-33074 is a high-severity use-after-free vulnerability in Qualcomm Snapdragon chipsets affecting audio components when a subsystem restart (SSR) event occurs after music playback stops. It can lead to memory corruption, potentially allowing an attacker to execute arbitrary code or cause denial of service without requiring user interaction or privileges. The vulnerability impacts a wide range of Snapdragon platforms, including mobile, wearable, and XR devices. No known exploits are currently reported in the wild. European organizations using devices with affected Snapdragon chipsets, especially in critical communication or IoT infrastructure, could face confidentiality, integrity, and availability risks. Mitigation requires timely firmware and software updates from device manufacturers and careful monitoring of SSR event handling. Countries with high smartphone and IoT adoption, such as Germany, France, and the UK, are most likely to be affected due to market penetration and strategic importance. Given the ease of exploitation and broad impact, this vulnerability is rated as high severity.