CVE-2023-48795

mediumPriorität · beachten · 67OT-Risiko · hochEPSS 0.935 · 100. PerzentilExploit · PoCCHDEEUNLRUUS
grimoire priorityP1 · Urgent
Exploitable?
Public exploit
4 exploits · PoC
Likely / severe?
93.5% (100th) EPSS
CVSS 5.9 · medium
Is it mine?
774 products
Prüfe deine Angriffsfläche
Who says so?
12 sources
cnnvd · enisa_euvd · fstec_bdu · osv

EPSS · bewertet 2026-10-22

The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other products, allows remote attackers to bypass integrity checks such that some packets are omitted (from the extension negotiation message), and a client and server may consequently end up with a connection for which some security features have been downgraded or disabled, aka a Terrapin attack. This occurs because the SSH Binary Packet Protocol (BPP), implemented by these extensions, mishandles the handshake phase and mishandles use of sequence numbers. For example, there is an effective attack against SSH's use of ChaCha20-Poly1305 (and CBC with Encrypt-then-MAC). The bypass occurs in chacha20-poly1305@openssh.com and (if CBC is used) the -etm@openssh.com MAC algorithms. This also affects Maverick Synergy Java SSH API before 3.1.0-SNAPSHOT, Dropbear through 2022.83, Ssh before 5.1.1 in Erlang/OTP, PuTTY before 0.80, AsyncSSH before 2.14.2, golang.org/x/crypto before 0.17.0, libssh before 0.10.6, libssh2 through 1.11.0, Thorn Tech SFTP Gateway before 3.4.6, Tera Term before 5.1, Paramiko before 3.4.0, jsch before 0.2.15, SFTPGo before 2.5.6, Netgate pfSense Plus through 23.09.1, Netgate pfSense CE through 2.7.2, HPN-SSH through 18.2.0, ProFTPD before 1.3.8b (and before 1.3.9rc2), ORYX CycloneSSH before 2.3.4, NetSarang XShell 7 before Build 0144, CrushFTP before 10.6.0, ConnectBot SSH library before 2.2.22, Apache MINA sshd through 2.11.0, sshj through 0.37.0, TinySSH through 20230101, trilead-ssh2 6401, LANCOM LCOS and LANconfig, FileZilla before 3.66.4, Nova before 11.8, PKIX-SSH before 14.4, SecureCRT before 9.4.3, Transmit5 before 5.10.4, Win32-OpenSSH before 9.5.0.0p1-Beta, WinSCP before 6.2.2, Bitvise SSH Server before 9.32, Bitvise SSH Client before 9.33, KiTTY through 0.76.1.13, the net-ssh gem 7.2.0 for Ruby, the mscdex ssh2 module before 1.15.0 for Node.js, the thrussh library before 0.35.1 for Rust, and the Russh crate before 0.40.2 for Rust.

01

Behebungen

Hersteller-Fix, Mitigation oder Workaround, wie von den Quellen veröffentlicht.

Ein Hersteller-Fix ist verfügbar.

  • BehobenRUGGEDCOM APE1808siemens_psirt

    Upgrade Palo Alto Networks Virtual NGFW V11.1.4-h1. Contact customer support to receive patch and update information

  • BehobenSCALANCE WAB762-1 (6GK5762-1AJ00-6AA0)siemens_psirt

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WAM763-1 (6GK5763-1AL00-7DA0)siemens_psirt

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WAM763-1 (ME) (6GK5763-1AL00-7DC0)siemens_psirt

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WAM763-1 (US) (6GK5763-1AL00-7DB0)siemens_psirt

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WAM766-1 (6GK5766-1GE00-7DA0)siemens_psirt

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WAM766-1 (ME) (6GK5766-1GE00-7DC0)siemens_psirt

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WAM766-1 (US) (6GK5766-1GE00-7DB0)siemens_psirt

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WAM766-1 EEC (6GK5766-1GE00-7TA0)siemens_psirt

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WAM766-1 EEC (ME) (6GK5766-1GE00-7TC0)siemens_psirt

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WAM766-1 EEC (US) (6GK5766-1GE00-7TB0)siemens_psirt

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WUB762-1 (6GK5762-1AJ00-1AA0)siemens_psirt

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WUB762-1 iFeatures (6GK5762-1AJ00-2AA0)siemens_psirt

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WUM763-1 (6GK5763-1AL00-3AA0)siemens_psirt

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WUM763-1 (6GK5763-1AL00-3DA0)siemens_psirt

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WUM763-1 (US) (6GK5763-1AL00-3AB0)siemens_psirt

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WUM763-1 (US) (6GK5763-1AL00-3DB0)siemens_psirt

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WUM766-1 (6GK5766-1GE00-3DA0)siemens_psirt

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WUM766-1 (ME) (6GK5766-1GE00-3DC0)siemens_psirt

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WUM766-1 (USA) (6GK5766-1GE00-3DB0)siemens_psirt

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSIMATIC S7-1500 TM MFP - GNU/Linux subsystemsiemens_psirt

    Update to V1.1 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109827684/
  • BehobenSINEC INSsiemens_psirt

    Update to V1.0 SP2 Update 3 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109975745/
  • Behobenwago_psirt

    A fix for the affected Firmwares will be provided with the following firmware versions: - FW22, Patch 2 installed on 750-810x - FW22, Patch 2 installed on 750-821x - FW22, Patch 2 installed on 762-4x0x - FW22, Patch 2 installed on 762-5x0x - FW22, Patch 2 installed on 762-6x0x - FW22, Patch 2 installed on 752-8303 - FW27 installed on 750-811x - FW27 installed on 750-821x - FW27 installed on 751-9301 - FW27 installed on 751-9401 - FW27 installed on 762-4x0x - FW27 installed on 762-5x0x - FW27 installed on 762-6x0x - FW27 installed on 752-8303 - Custom Firmware 03.03.08 (80) installed on 750-820x - Custom Firmware 04.03.03 (72) installed on 751-9301 - Custom Firmware 04.03.03 (72) installed on 751-9401 - Custom Firmware 04.04.03 (70) installed on 750-821x

  • Behobenphoenix_contact_psirt

    Update to the latest 2024.0.6 LTS Firmware Release. PHOENIX CONTACT recommends to always use an up-to-date version of the PLCnext Engineer.

  • BehobenSIMATIC S7-1500 TM MFP - GNU/Linux subsystemcisa_csaf_ot

    Update to V1.1 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109827684/
  • BehobenRUGGEDCOM APE1808cisa_csaf_ot

    Upgrade Palo Alto Networks Virtual NGFW V11.1.4-h1. Contact customer support to receive patch and update information

  • BehobenSINEC INScisa_csaf_ot

    Update to V1.0 SP2 Update 3 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109975745/
  • BehobenSCALANCE WAB762-1 (6GK5762-1AJ00-6AA0)cisa_csaf_ot

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WAM763-1 (6GK5763-1AL00-7DA0)cisa_csaf_ot

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WAM763-1 (ME) (6GK5763-1AL00-7DC0)cisa_csaf_ot

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WAM763-1 (US) (6GK5763-1AL00-7DB0)cisa_csaf_ot

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WAM766-1 (6GK5766-1GE00-7DA0)cisa_csaf_ot

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WAM766-1 (ME) (6GK5766-1GE00-7DC0)cisa_csaf_ot

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WAM766-1 (US) (6GK5766-1GE00-7DB0)cisa_csaf_ot

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WAM766-1 EEC (6GK5766-1GE00-7TA0)cisa_csaf_ot

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WAM766-1 EEC (ME) (6GK5766-1GE00-7TC0)cisa_csaf_ot

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WAM766-1 EEC (US) (6GK5766-1GE00-7TB0)cisa_csaf_ot

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WUB762-1 (6GK5762-1AJ00-1AA0)cisa_csaf_ot

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WUB762-1 iFeatures (6GK5762-1AJ00-2AA0)cisa_csaf_ot

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WUM763-1 (6GK5763-1AL00-3AA0)cisa_csaf_ot

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WUM763-1 (6GK5763-1AL00-3DA0)cisa_csaf_ot

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WUM763-1 (US) (6GK5763-1AL00-3AB0)cisa_csaf_ot

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WUM763-1 (US) (6GK5763-1AL00-3DB0)cisa_csaf_ot

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WUM766-1 (6GK5766-1GE00-3DA0)cisa_csaf_ot

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WUM766-1 (ME) (6GK5766-1GE00-3DC0)cisa_csaf_ot

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • BehobenSCALANCE WUM766-1 (USA) (6GK5766-1GE00-3DB0)cisa_csaf_ot

    Update to V3.0.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109977720/
  • MitigationARM600abb_psirt

    Mitigating factors describe conditions and circumstances that make an attack that exploits the vulnerability difficult or less likely to succeed. The following mitigations are recommended. 1. Obtain a cellular private access point (APN). A dedicated private cellular access point and respective SIM card subscriptions can be requested from your cellular service provider. This service doesn’t expose the traffic between remote sites and main site to the internet but rather uses cellular operator’s private wide area network (WAN). Therefore, the ARM600 wouldn’t need open ports to the internet. 2. Avoid exposing any system component to the internet. If, however, the ARM600 is exposed to the internet, only the VPN port should be opened towards the internet (e.g., Patrol management connections can be configured to use VPN tunnel and remote administration connections can be implemented by using OpenVPN PC-client). 4. Perform firewall configuration by the "allowlisting" principle, i.e., explicitly allowing only the required ports and protocols and blocking any other traffic. 6. If the internet is used as a WAN media for carrying VPN tunnels, use Demilitarized Zone (DMZ) for terminating connections from the internet (i.e., the remote connections should terminate to the DMZ network, which would be segregated from other networks by a firewall. The ARM600 server would be located into this DMZ). 7. Change the default user credentials of ARM600 and Arctic wireless gateways into non-defaults and use complex non-guessable passwords with special characters. Do not reuse passwords within the system. 8. Use administrator (i.e., root user) privileges only when required by the task. 9. Supporting systems, such as PCs used for configuration, should be frequently updated. If possible, use dedicated site PCs for upgrading and engineering purposes. At minimum, PCs should be investigated by running a full virus scan with recently updated signature files before introducing the PC to the OT system. Any data, such as device configurations and firmware update files transferred to the Arctic system should be virus scanned prior to transferring. 10. Introduce a backup policy, which will ensure periodical backups and backup revision numbering. Consider the following: a. Check that the entire system has backups available from all applicable parts. b. Store the backups in a safe place (e.g. in an encrypted storage), restricted by role-based access control mechanisms. c. Ensure the security of the configuration PCs that may have local copies of device configurations. d. Validate the backups to make sure that they’re working. 11. Follow cyber security best practices for installation, operation, and decommissioning as described in the product’s Cyber Security Deployment Guideline and User Manual. 12. Use continuous monitoring (e.g., intrusion detection/prevention tools) to detect anomalies in the system 13. Consider hardening the system according to the following: a. Remove any unnecessary communication links in the system. b. If possible, close unused physical ports. c. Open only the necessary TCP/UDP ports in the configuration. d. Remove all unnecessary user accounts. e. Restrict traffic by firewall. f. Allow the traffic only from/to necessary hosts' IP addresses (i.e., define both source and destination in the firewall rules, where possible). g. Define client IP address as allowed address in SCADA communication protocols, if such configuration is supported. h. Remove or deactivate all unused processes, communication ports and services, where possible. i. Use physical access controls to the system installations (e.g., to server rooms and device cabinets).

  • MitigationSWabb_psirt

    Mitigating factors describe conditions and circumstances that make an attack that exploits the vulnerability difficult or less likely to succeed. The following mitigations are recommended. 1. Obtain a cellular private access point (APN). A dedicated private cellular access point and respective SIM card subscriptions can be requested from your cellular service provider. This service doesn’t expose the traffic between remote sites and main site to the internet but rather uses cellular operator’s private wide area network (WAN). Therefore, the ARM600 wouldn’t need open ports to the internet. 2. Avoid exposing any system component to the internet. If, however, the ARM600 is exposed to the internet, only the VPN port should be opened towards the internet (e.g., Patrol management connections can be configured to use VPN tunnel and remote administration connections can be implemented by using OpenVPN PC-client). 4. Perform firewall configuration by the "allowlisting" principle, i.e., explicitly allowing only the required ports and protocols and blocking any other traffic. 6. If the internet is used as a WAN media for carrying VPN tunnels, use Demilitarized Zone (DMZ) for terminating connections from the internet (i.e., the remote connections should terminate to the DMZ network, which would be segregated from other networks by a firewall. The ARM600 server would be located into this DMZ). 7. Change the default user credentials of ARM600 and Arctic wireless gateways into non-defaults and use complex non-guessable passwords with special characters. Do not reuse passwords within the system. 8. Use administrator (i.e., root user) privileges only when required by the task. 9. Supporting systems, such as PCs used for configuration, should be frequently updated. If possible, use dedicated site PCs for upgrading and engineering purposes. At minimum, PCs should be investigated by running a full virus scan with recently updated signature files before introducing the PC to the OT system. Any data, such as device configurations and firmware update files transferred to the Arctic system should be virus scanned prior to transferring. 10. Introduce a backup policy, which will ensure periodical backups and backup revision numbering. Consider the following: a. Check that the entire system has backups available from all applicable parts. b. Store the backups in a safe place (e.g. in an encrypted storage), restricted by role-based access control mechanisms. c. Ensure the security of the configuration PCs that may have local copies of device configurations. d. Validate the backups to make sure that they’re working. 11. Follow cyber security best practices for installation, operation, and decommissioning as described in the product’s Cyber Security Deployment Guideline and User Manual. 12. Use continuous monitoring (e.g., intrusion detection/prevention tools) to detect anomalies in the system 13. Consider hardening the system according to the following: a. Remove any unnecessary communication links in the system. b. If possible, close unused physical ports. c. Open only the necessary TCP/UDP ports in the configuration. d. Remove all unnecessary user accounts. e. Restrict traffic by firewall. f. Allow the traffic only from/to necessary hosts' IP addresses (i.e., define both source and destination in the firewall rules, where possible). g. Define client IP address as allowed address in SCADA communication protocols, if such configuration is supported. h. Remove or deactivate all unused processes, communication ports and services, where possible. i. Use physical access controls to the system installations (e.g., to server rooms and device cabinets).

  • MitigationSIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0)siemens_psirt

    Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.

  • MitigationSIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0)siemens_psirt

    Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.

  • MitigationSIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0)siemens_psirt

    Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.

  • MitigationSIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0)siemens_psirt

    Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.

  • MitigationSIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0)siemens_psirt

    Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.

  • MitigationRUGGEDCOM APE1808siemens_psirt

    Configure the RADIUS server to require the presence of a Message-Authenticator attribute in all Access-Request packets from RADIUS client devices that support it

  • MitigationSIMATIC S7-1500 TM MFP - GNU/Linux subsystemsiemens_psirt

    Only build and run applications from trusted sources

  • MitigationRUGGEDCOM APE1808cisa_csaf_ot

    Configure the RADIUS server to require the presence of a Message-Authenticator attribute in all Access-Request packets from RADIUS client devices that support it

  • MitigationARM600cisa_csaf_ot

    Mitigating factors describe conditions and circumstances that make an attack that exploits the vulnerability difficult or less likely to succeed. The following mitigations are recommended. 1. Obtain a cellular private access point (APN). A dedicated private cellular access point and respective SIM card subscriptions can be requested from your cellular service provider. This service doesn’t expose the traffic between remote sites and main site to the internet but rather uses cellular operator’s private wide area network (WAN). Therefore, the ARM600 wouldn’t need open ports to the internet. 2. Avoid exposing any system component to the internet. If, however, the ARM600 is exposed to the internet, only the VPN port should be opened towards the internet (e.g., Patrol management connections can be configured to use VPN tunnel and remote administration connections can be implemented by using OpenVPN PC-client). 4. Perform firewall configuration by the "allowlisting" principle, i.e., explicitly allowing only the required ports and protocols and blocking any other traffic. 6. If the internet is used as a WAN media for carrying VPN tunnels, use Demilitarized Zone (DMZ) for terminating connections from the internet (i.e., the remote connections should terminate to the DMZ network, which would be segregated from other networks by a firewall. The ARM600 server would be located into this DMZ). 7. Change the default user credentials of ARM600 and Arctic wireless gateways into non-defaults and use complex non-guessable passwords with special characters. Do not reuse passwords within the system. 8. Use administrator (i.e., root user) privileges only when required by the task. 9. Supporting systems, such as PCs used for configuration, should be frequently updated. If possible, use dedicated site PCs for upgrading and engineering purposes. At minimum, PCs should be investigated by running a full virus scan with recently updated signature files before introducing the PC to the OT system. Any data, such as device configurations and firmware update files transferred to the Arctic system should be virus scanned prior to transferring. 10. Introduce a backup policy, which will ensure periodical backups and backup revision numbering. Consider the following: a. Check that the entire system has backups available from all applicable parts. b. Store the backups in a safe place (e.g. in an encrypted storage), restricted by role-based access control mechanisms. c. Ensure the security of the configuration PCs that may have local copies of device configurations. d. Validate the backups to make sure that they’re working. 11. Follow cyber security best practices for installation, operation, and decommissioning as described in the product’s Cyber Security Deployment Guideline and User Manual. 12. Use continuous monitoring (e.g., intrusion detection/prevention tools) to detect anomalies in the system 13. Consider hardening the system according to the following: a. Remove any unnecessary communication links in the system. b. If possible, close unused physical ports. c. Open only the necessary TCP/UDP ports in the configuration. d. Remove all unnecessary user accounts. e. Restrict traffic by firewall. f. Allow the traffic only from/to necessary hosts' IP addresses (i.e., define both source and destination in the firewall rules, where possible). g. Define client IP address as allowed address in SCADA communication protocols, if such configuration is supported. h. Remove or deactivate all unused processes, communication ports and services, where possible. i. Use physical access controls to the system installations (e.g., to server rooms and device cabinets).

  • MitigationSWcisa_csaf_ot

    Mitigating factors describe conditions and circumstances that make an attack that exploits the vulnerability difficult or less likely to succeed. The following mitigations are recommended. 1. Obtain a cellular private access point (APN). A dedicated private cellular access point and respective SIM card subscriptions can be requested from your cellular service provider. This service doesn’t expose the traffic between remote sites and main site to the internet but rather uses cellular operator’s private wide area network (WAN). Therefore, the ARM600 wouldn’t need open ports to the internet. 2. Avoid exposing any system component to the internet. If, however, the ARM600 is exposed to the internet, only the VPN port should be opened towards the internet (e.g., Patrol management connections can be configured to use VPN tunnel and remote administration connections can be implemented by using OpenVPN PC-client). 4. Perform firewall configuration by the "allowlisting" principle, i.e., explicitly allowing only the required ports and protocols and blocking any other traffic. 6. If the internet is used as a WAN media for carrying VPN tunnels, use Demilitarized Zone (DMZ) for terminating connections from the internet (i.e., the remote connections should terminate to the DMZ network, which would be segregated from other networks by a firewall. The ARM600 server would be located into this DMZ). 7. Change the default user credentials of ARM600 and Arctic wireless gateways into non-defaults and use complex non-guessable passwords with special characters. Do not reuse passwords within the system. 8. Use administrator (i.e., root user) privileges only when required by the task. 9. Supporting systems, such as PCs used for configuration, should be frequently updated. If possible, use dedicated site PCs for upgrading and engineering purposes. At minimum, PCs should be investigated by running a full virus scan with recently updated signature files before introducing the PC to the OT system. Any data, such as device configurations and firmware update files transferred to the Arctic system should be virus scanned prior to transferring. 10. Introduce a backup policy, which will ensure periodical backups and backup revision numbering. Consider the following: a. Check that the entire system has backups available from all applicable parts. b. Store the backups in a safe place (e.g. in an encrypted storage), restricted by role-based access control mechanisms. c. Ensure the security of the configuration PCs that may have local copies of device configurations. d. Validate the backups to make sure that they’re working. 11. Follow cyber security best practices for installation, operation, and decommissioning as described in the product’s Cyber Security Deployment Guideline and User Manual. 12. Use continuous monitoring (e.g., intrusion detection/prevention tools) to detect anomalies in the system 13. Consider hardening the system according to the following: a. Remove any unnecessary communication links in the system. b. If possible, close unused physical ports. c. Open only the necessary TCP/UDP ports in the configuration. d. Remove all unnecessary user accounts. e. Restrict traffic by firewall. f. Allow the traffic only from/to necessary hosts' IP addresses (i.e., define both source and destination in the firewall rules, where possible). g. Define client IP address as allowed address in SCADA communication protocols, if such configuration is supported. h. Remove or deactivate all unused processes, communication ports and services, where possible. i. Use physical access controls to the system installations (e.g., to server rooms and device cabinets).

  • MitigationSIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0)cisa_csaf_ot

    Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.

  • MitigationSIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0)cisa_csaf_ot

    Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.

  • MitigationSIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0)cisa_csaf_ot

    Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.

  • MitigationSIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0)cisa_csaf_ot

    Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.

  • MitigationSIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0)cisa_csaf_ot

    Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.

  • WorkaroundSIMATIC S7-1500 TM MFP - GNU/Linux subsystemcisa_csaf_ot

    Only build and run applications from trusted sources

  • Kein Fix verfügbarSIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0)siemens_psirt

    Currently no fix is available

  • Kein Fix verfügbarSIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0)siemens_psirt

    Currently no fix is available

  • Kein Fix verfügbarSIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0)siemens_psirt

    Currently no fix is available

  • Kein Fix verfügbarSIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0)siemens_psirt

    Currently no fix is available

  • Kein Fix verfügbarSIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0)siemens_psirt

    Currently no fix is available

  • Kein Fix verfügbarSIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0)cisa_csaf_ot

    Currently no fix is available

  • Kein Fix verfügbarSIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0)cisa_csaf_ot

    Currently no fix is available

  • Kein Fix verfügbarSIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0)cisa_csaf_ot

    Currently no fix is available

  • Kein Fix verfügbarSIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0)cisa_csaf_ot

    Currently no fix is available

  • Kein Fix verfügbarSIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0)cisa_csaf_ot

    Currently no fix is available

02

cvss

Technischer Schweregrad, 0–10. Eine Zeile je Quelle.

7.4
010

Basiswert 0–10 · höher = schwerwiegender · Vektor überfahren zum Auflösen⚠ Quellen uneinig · medium–high · 5.9–7.4

v3.15.9mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:Nprimary · NVD / NIST USAusnutzbarkeit 2.2 · Auswirkung 3.6
v3.15.9mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:Nsecondary · CISA US
v3.17.4highAV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:Nsecondary · FSTEC (BDU) RU
v3.15.9mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:Nsecondary · ENISA EU
v3.15.9mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:NsecondaryAusnutzbarkeit 2.2 · Auswirkung 3.6
v3.15.9mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:Nsecondary · OSV
v3.15.9mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:Nsecondary · Siemens ProductCERT DE
v3.15.9mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:Nsecondary · Phoenix Contact PSIRT DE
v3.15.9mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:Nsecondary · WAGO PSIRT DE
v3.15.9mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:Nsecondary · SICK PSIRT DE
v3.15.9mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N/E:Hsecondary · CVSS-BT (t0sche)
v3.15.9mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N/E:P/RL:W/RC:Csecondary · ABB PSIRT
v3.15.9mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:Nsecondary · NCSC-NL NL
03

SSVC

Eine Handlungsentscheidung — aus Ausnutzung und Auswirkung.

Exploitation: poc · Automatable: no · Technical Impact: partialcoordinatorcisa_ssvcUS
04

schwächen

Die CWE-Schwächeklassen, zu denen dies gehört.

CWE-354USprimärCWE-222USCWE-222USCWE-222USCWE-222USCWE-345USCWE-354USCWE-354USCWE-354USCWE-354USCWE-354USCWE-354USCWE-354US
05

Exploits (4)

Öffentlicher Proof-of-Concept- und Exploit-Code.

06

betroffene Produkte (774)

Betroffene Produkte und Versionsbereiche.

20 von 774 angezeigt
07

Advisories (74)

Hersteller- und Ökosystem-Meldungen dazu.

  • 2NGA002579ABB Arctic communication solution ARM600 Vulnerabilities2025-04-07csaf · abb_psirtCH

    ABB is aware of public reports of a vulnerabilities in product versions listed as affected in this advisory. An attacker who successfully exploited these vulnerabilities could cause the product to stop, make the product inacces-sible, take remote control of the product or insert and run arbitrary code. As part of ABB product lifecycle policy, once a product transitions to end-of-life, we discontinue maintenance, security patches, and technical support to focus on current and future technologies. While the product will continue to function, we strongly recommend implementing mitigations defined in this document, such as using a private APN cellular network between Arctic wireless gateways and ARM600 for establishing VPN tunnels, to mitigate security risks and avoid potential vulnerabilities. As part of ABB product lifecycle policy, once a product transitions to Limited state, we discontinue maintenance, security patches, and technical support to focus on current and future technologies. While the product will continue to function, we strongly recommend implementing mitigations defined in this document to mitigate security risks.

  • NCSC-2024-0282Kwetsbaarheden verholpen in Siemens ProductenNL2024-07-09csaf · ncsc_nlNL

    Siemens heeft kwetsbaarheden verholpen in diverse producten als Mendix, RUGGEDOM, SIMATIC, SINEMA, SIPROTEC en de Engineering Platforms voor diverse systemen.

  • NCSC-2024-0293Kwetsbaarheden verholpen in Oracle Communications ApplicationsNL2024-07-17csaf · ncsc_nlNL

    Er zijn kwetsbaarheden verholpen in Oracle Communications Applications.

  • NCSC-2024-0294Kwetsbaarheden verholpen in Oracle CommunicationsNL2024-07-17csaf · ncsc_nlNL

    Er zijn kwetsbaarheden verholpen in Oracle Communications.

  • NCSC-2024-0296Kwetsbaarheden verholpen in Oracle Enterprise ManagerNL2024-07-17csaf · ncsc_nlNL

    Er zijn kwetsbaarheden verholpen in Oracle Enterprise Manager.

  • NCSC-2024-0298 Kwetsbaarheden verholpen in Oracle Fusion MiddlewareNL2024-07-17csaf · ncsc_nlNL

    Er zijn kwetsbaarheden verholpen in Oracle Fusion Middleware.

  • NCSC-2024-0299 Kwetsbaarheden verholpen in Oracle AnalyticsNL2024-07-17csaf · ncsc_nlNL

    Er zijn kwetsbaarheden verholpen in Oracle Analytics.

  • NCSC-2024-0303Kwetsbaarheden verholpen in Oracle MySQLNL2024-07-17csaf · ncsc_nlNL

    Er zijn kwetsbaarheden verholpen in Oracle MySQL.

  • NCSC-2024-0304Kwetsbaarheden verholpen in Oracle PeopleSoftNL2024-07-17csaf · ncsc_nlNL

    Er zijn kwetsbaarheden verholpen in Oracle PeopleSoft.

  • NCSC-2024-0325Kwetsbaarheden verholpen in Aruba Networks ArubaOS en InstantOSNL2024-08-07csaf · ncsc_nlNL

    Aruba Networks heeft kwetsbaarheden verholpen in ArubaOS en InstantOS.

  • NCSC-2024-0411Kwetsbaarheden verholpen in Oracle Database productenNL2024-10-17csaf · ncsc_nlNL

    Oracle heeft kwetsbaarheden verholpen in diverse Database producten en subsystemen, zoals de Core database, Application Express, Autonomous Health Framework, Essbase, GoldenGate, SQL Developer en Secure Backup.

  • NCSC-2024-0414Kwetsbaarheden verholpen in Oracle CommunicationsNL2024-10-17csaf · ncsc_nlNL

    Oracle heeft kwetsbaarheden verholpen in diverse Communications producten en systemen.

  • NCSC-2024-0433Kwetsbaarheden verholpen in Siemens productenNL2024-11-12csaf · ncsc_nlNL

    Siemens heeft kwetsbaarheden verholpen in diverse producten als Mendix, RUGGEDCOM, SCALANCE, SIMATIC en SINEC.

  • NCSC-2025-0020Kwetsbaarheden verholpen in Oracle Database productenNL2025-01-22csaf · ncsc_nlNL

    Oracle heeft kwetsbaarheden verholpen in diverse database producten en subsystemen, zoals de Core Database, Graal, Application Express, GoldenGate en REST data.

  • NCSC-2025-0023Kwetsbaarheden verholpen in Oracle PeopleSoftNL2025-01-22csaf · ncsc_nlNL

    Oracle heeft meerdere kwetsbaarheden verholpen in Oracle PeopleSoft, specifiek in de versies 8.60, 8.61 en 9.2.

  • NCSC-2025-0025Kwetsbaarheden verholpen in Oracle Financial ServicesNL2025-01-22csaf · ncsc_nlNL

    Oracle heeft meerdere kwetsbaarheden verholpen in Financial Services en componenten.

  • NCSC-2025-0026Kwetsbaarheden verholpen in Oracle JD EdwardsNL2025-01-22csaf · ncsc_nlNL

    Oracle heeft kwetsbaarheden verholpen in JD Edwards EnterpriseOne Tools (specifiek voor versies prior tot 9.2.9.2).

  • NCSC-2025-0061Kwetsbaarheden verholpen in Siemens productenNL2025-02-14csaf · ncsc_nlNL

    Siemens heeft kwetsbaarheden verholpen in diverse producten als APOGEE, Opcenter, RUGGEDCOM, SCALANCE, SIMATIC, SIPROTEC en Teamcenter.

  • NCSC-2025-0166Kwetsbaarheden verholpen in Fortinet productenNL2025-05-14csaf · ncsc_nlNL

    Fortinet heeft kwetsbaarheden verholpen in FortiManager, FortiManager Cloud, FortiAnalyzer, FortiOS, FortiProxy, FortiPAM, FortiSRA, FortiSwitchManager en FortiWeb.

  • NCSC-2025-0187Kwetsbaarheden verholpen in Siemens productenNL2025-06-10csaf · ncsc_nlNL

    Siemens heeft kwetsbaarheden verholpen in diverse producten als RUGGEDCOM, SCALANCE, SIMATIC en Tecnomatix

  • SCA-2025-0009Vulnerabilities affecting SICK TDC-E210GC2025-08-01csaf · sick_psirtDE

    SICK has identified multiple vulnerabilities in the SICK TDC-E210GC product. The advisory includes a total of 23 vulnerabilities, of which 14 are confirmed as affected and 9 as known not affected. At this time, SICK is not aware of any public exploits specifically targeting these vulnerabilities. Customers are strongly advised to apply the recommended workaround for the affected vulnerabilities to reduce potential risk.

  • SCA-2025-0011Vulnerabilities affecting Endress+Hauser SSG-E210GC2025-10-02csaf · sick_psirtDE

    Several vulnerabilities in the Endress+Hauser SSG-E210GC product were discoverd. The advisory includes a total of 23 vulnerabilities, of which 14 are confirmed as affected and 9 as known not affected.

  • SSA-082556SSA-082556: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.52025-06-10csaf · siemens_psirtDE

    Multiple vulnerabilities have been identified in the additional GNU/Linux subsystem of the firmware version V3.1.5 for the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP (incl. SIPLUS variant). Siemens has released new versions for several affected products and recommends to update to the latest versions. Siemens is preparing further fixes and recommends specific mitigations for products where fixes are not or not yet available. SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.5 is no longer maintained and there won't be any update to the CVE list anymore. Please update to the latest version. Note: This SSA advises vulnerabilities for firmware version V3.1.5 only; for version V3.1.6 refer to SSA-019113.

  • SSA-364175SSA-364175: Multiple Vulnerabilities in Palo Alto Networks Virtual NGFW on RUGGEDCOM APE1808 Devices Before V11.1.4-h12024-07-09csaf · siemens_psirtDE

    Palo Alto Networks has published [1] information on vulnerabilities in PAN-OS. This advisory lists the related Siemens Industrial products affected by these vulnerabilities. Siemens is preparing updates and recommends specific countermeasures for products where updates are not, or not yet available. Customers are advised to consult and implement the workarounds provided in Palo Alto Networks' upstream security notifications. [1] https://security.paloaltonetworks.com/

  • SSA-769027SSA-769027: Multiple Vulnerabilities fixed in SCALANCE W700 IEEE 802.11ax devices before V3.0.02025-02-11csaf · siemens_psirtDE

    SCALANCE W-700 IEEE 802.11ax family devices are affected by multiple vulnerabilities. Siemens has released new versions for the affected products and recommends to update to the latest versions.

  • SSA-794697SSA-794697: Vulnerabilities in the Additional GNU/Linux Subsystem of the SIMATIC S7-1500 TM MFP Before V1.12023-06-13csaf · siemens_psirtDE

    Multiple vulnerabilities have been identified in the additional GNU/Linux subsystem of the SIMATIC S7-1500 TM MFP V1.0. Siemens has released a new version for SIMATIC S7-1500 TM MFP - GNU/Linux subsystem and recommends to update to the latest version. SIMATIC S7-1500 TM MFP V1.0 is no longer maintained and there won't be any update to the CVE list anymore. Please update to the latest version. This advisory lists vulnerabilities for firmware version V1.0 only; for V1.1 refer to Siemens Security Advisory SSA-265688 (https://cert-portal.siemens.com/productcert/html/ssa-265688.html).

  • SSA-915275SSA-915275: Multiple Vulnerabilities in SINEC INS Before V1.0 SP2 Update 32024-11-12csaf · siemens_psirtDE

    SINEC INS before V1.0 SP2 Update 3 is affected by multiple vulnerabilities. Siemens has released a new version for SINEC INS and recommends to update to the latest version.

  • VDE-2024-014WAGO: Multiple products affected by Terrapin2024-02-22csaf · wago_psirtDE

    Several WAGO Firmwares are vulnerable to a to a remote attack which allows to bypass the integrity check through OpenSSH. This called Terrapin attack occurs because of mishandled handshake phase.

  • VDE-2024-073Phoenix Contact: Multiple Vulnerabilities in PLCnext Firmware2024-12-09csaf · phoenix_contact_psirtDE

    Multiple Linux component vulnerabilities fixed in latest PLCnext Firmware release 2024.0.6 LTS

  • WID-SEC-W-2023-3174SSH Protokoll: Schwachstelle ermöglicht Umgehen von SicherheitsvorkehrungenDeutsch2023-12-18csaf · cert_bundDE

    Ein entfernter, anonymer Angreifer kann eine Schwachstelle im SSH Protokoll ausnutzen, um Sicherheitsvorkehrungen zu umgehen.

  • WID-SEC-W-2024-0523SolarWinds Security Event Manager: Mehrere SchwachstellenDeutsch2024-02-29csaf · cert_bundDE

    Ein entfernter, anonymer oder authentifizierter Angreifer kann mehrere Schwachstellen in SolarWinds Security Event Manager ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen preiszugeben und einen Denial-of-Service-Zustand zu verursachen.

  • WID-SEC-W-2024-0564Jenkins: Mehrere SchwachstellenDeutsch2024-03-06csaf · cert_bundDE

    Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Jenkins ausnutzen, um Sicherheitsvorkehrungen zu umgehen, Informationen offenzulegen, Dateien zu manipulieren oder einen Cross-Site-Scripting-Angriff durchzuführen.

  • WID-SEC-W-2024-0578Apple macOS: Mehrere SchwachstellenDeutsch2024-03-07csaf · cert_bundDE

    Ein entfernter anonymer Angreifer kann mehrere Schwachstellen in Apple macOS ausnutzen, um vertrauliche Informationen offenzulegen, Dateien zu manipulieren, einen Denial-of-Service-Zustand zu verursachen, beliebigen Code auszuführen, seine Privilegien zu erweitern oder Sicherheitsmaßnahmen zu umgehen.

  • WID-SEC-W-2024-0869Oracle Communications: Mehrere SchwachstellenDeutsch2024-04-16csaf · cert_bundDE

    Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Oracle Communications ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

  • WID-SEC-W-2024-0874Oracle Enterprise Manager: Mehrere SchwachstellenDeutsch2024-04-16csaf · cert_bundDE

    Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Enterprise Manager ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

  • WID-SEC-W-2024-0885Oracle Database Server: Mehrere SchwachstellenDeutsch2024-04-16csaf · cert_bundDE

    Ein Angreifer kann mehrere Schwachstellen in Oracle Database Server ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

  • WID-SEC-W-2024-0889Oracle Support Tools: Mehrere SchwachstellenDeutsch2024-04-16csaf · cert_bundDE

    Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Oracle Support Tools ausnutzen, um die Integrität und Verfügbarkeit zu gefährden.

  • WID-SEC-W-2024-0892Oracle Retail Applications: Mehrere SchwachstellenDeutsch2024-04-16csaf · cert_bundDE

    Ein Angreifer kann mehrere Schwachstellen in Oracle Retail Applications ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

  • WID-SEC-W-2024-0899Oracle Fusion Middleware: Mehrere SchwachstellenDeutsch2024-04-16csaf · cert_bundDE

    Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Oracle Fusion Middleware ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

  • WID-SEC-W-2024-1082Juniper JUNOS: Mehrere SchwachstellenDeutsch2024-05-09csaf · cert_bundDE

    Ein Angreifer kann mehrere Schwachstellen in Juniper JUNOS im Zusammenhang mit OpenSSH ausnutzen, um Sicherheitsmaßnahmen zu umgehen, beliebigen Code auszuführen oder Dateien zu manipulieren.

  • WID-SEC-W-2024-1186IBM DB2 REST: Mehrere SchwachstellenDeutsch2024-05-20csaf · cert_bundDE

    Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in IBM DB2 REST ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen oder einen Denial-of-Service-Zustand zu verursachen.

  • WID-SEC-W-2024-1228Red Hat OpenStack: Mehrere SchwachstellenDeutsch2024-05-22csaf · cert_bundDE

    Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Red Hat OpenStack ausnutzen, um Sicherheitsmaßnahmen zu umgehen, eine Denial-of-Service-Zustand zu erzeugen, um vertrauliche Informationen offenzulegen und Daten zu ändern.

  • WID-SEC-W-2024-1248Xerox FreeFlow Print Server: Mehrere SchwachstellenDeutsch2024-05-28csaf · cert_bundDE

    Ein Angreifer kann mehrere Schwachstellen in Xerox FreeFlow Print Server ausnutzen, um die Vertraulichkeit, Verfügbarkeit und Integrität des Systems zu gefährden

  • WID-SEC-W-2024-1474Red Hat OpenShift Container Platform: Mehrere SchwachstellenDeutsch2024-06-27csaf · cert_bundDE

    Ein entfernter, anonymer oder lokaler Angreifer kann mehrere Schwachstellen in Red Hat OpenShift ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen, vertrauliche Informationen offenzulegen oder Daten zu manipulieren.

  • WID-SEC-W-2024-1630Oracle NoSQL Database: Schwachstelle gefährdet IntegritätDeutsch2024-07-16csaf · cert_bundDE

    Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Oracle NoSQL Database ausnutzen, um die Integrität zu gefährden.

  • WID-SEC-W-2024-1637Oracle Fusion Middleware: Mehrere SchwachstellenDeutsch2024-07-16csaf · cert_bundDE

    Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Fusion Middleware ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

  • WID-SEC-W-2024-1639Oracle Enterprise Manager: Mehrere SchwachstellenDeutsch2024-07-16csaf · cert_bundDE

    Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Oracle Enterprise Manager ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

  • WID-SEC-W-2024-1642Oracle Communications: Mehrere SchwachstellenDeutsch2024-07-16csaf · cert_bundDE

    Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Communications ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

  • WID-SEC-W-2024-1643Oracle Communications Applications: Mehrere SchwachstellenDeutsch2024-07-16csaf · cert_bundDE

    Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Communications Applications ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

  • WID-SEC-W-2024-1655Oracle PeopleSoft: Mehrere SchwachstellenDeutsch2024-07-16csaf · cert_bundDE

    Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle PeopleSoft ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

  • WID-SEC-W-2024-1656Oracle MySQL: Mehrere SchwachstellenDeutsch2024-07-16csaf · cert_bundDE

    Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle MySQL ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

  • WID-SEC-W-2024-1701Aruba EdgeConnect: Mehrere SchwachstellenDeutsch2024-07-23csaf · cert_bundDE

    Ein entfernter Angreifer kann mehrere Schwachstellen in Aruba EdgeConnect ausnutzen, um beliebigen Code auszuführen oder um Sicherheitsmaßnahmen zu umgehen.

  • WID-SEC-W-2024-1781Aruba ArubaOS: Mehrere Schwachstellen ermöglichen Codeausführung und DOSDeutsch2024-08-06csaf · cert_bundDE

    Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Aruba ArubaOS ausnutzen, um beliebigen Programmcode auszuführen und einen Denial-of-Service-Zustand zu erzeugen.

  • WID-SEC-W-2024-1913Red Hat OpenShift Container Platform: Mehrere SchwachstellenDeutsch2024-08-22csaf · cert_bundDE

    Ein entfernter anonymer oder lokaler Angreifer kann mehrere Schwachstellen in Red Hat OpenShift Container Platform ausnutzen, um seine Privilegien zu erhöhen, beliebigen Code auszuführen, einen Denial-of-Service-Zustand zu erzeugen, vertrauliche Informationen offenzulegen, Dateien und Daten zu manipulieren oder Sicherheitsmaßnahmen zu umgehen.

  • WID-SEC-W-2024-3195Oracle Communications: Mehrere SchwachstellenDeutsch2024-10-15csaf · cert_bundDE

    Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Communications ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

  • WID-SEC-W-2024-3198Oracle SQL Developer: Schwachstelle gefährdet IntegritätDeutsch2024-10-15csaf · cert_bundDE

    Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Oracle SQL Developer ausnutzen, um die Integrität zu gefährden.

  • WID-SEC-W-2024-3320Moxa Ethernet Switches: Mehrere SchwachstellenDeutsch2024-10-31csaf · cert_bundDE

    Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Moxa Ethernet Switches ausnutzen, um Informationen offenzulegen oder Sicherheitsmaßnahmen zu umgehen.

  • WID-SEC-W-2024-3377Dell PowerProtect Data Domain: Mehrere SchwachstellenDeutsch2024-11-07csaf · cert_bundDE

    Ein lokaler Angreifer kann mehrere Schwachstellen in Dell PowerProtect Data Domain ausnutzen, um seine Privilegien zu erhöhen, Informationen offenzulegen und um nicht näher beschriebene Auswirkungen zu erzielen.

  • WID-SEC-W-2025-0139Oracle Database Server: Mehrere SchwachstellenDeutsch2025-01-21csaf · cert_bundDE

    Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Database Server ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

  • WID-SEC-W-2025-0144Oracle Financial Services Applications: Mehrere SchwachstellenDeutsch2025-01-21csaf · cert_bundDE

    Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Financial Services Applications ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

  • WID-SEC-W-2025-0168Oracle JD Edwards: Mehrere SchwachstellenDeutsch2025-01-21csaf · cert_bundDE

    Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle JD Edwards ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

  • WID-SEC-W-2025-0810Oracle Retail Applications: Mehrere SchwachstellenDeutsch2025-04-15csaf · cert_bundDE

    Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Oracle Retail Applications ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

  • WID-SEC-W-2026-1032IBM Tivoli Network Manager: Mehrere SchwachstellenDeutsch2026-04-08csaf · cert_bundDE

    Ein Angreifer kann mehrere Schwachstellen in IBM Tivoli Network Manager ausnutzen, um beliebigen Programmcode auszuführen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, und um Sicherheitsvorkehrungen zu umgehen.

  • GHSA-45x7-px36-x8w8Prefix Truncation Attack against ChaCha20-Poly1305 and Encrypt-then-MAC aka Terrapin2023-12-18ghsa · osvUS

    ### Summary Terrapin is a prefix truncation attack targeting the SSH protocol. More precisely, Terrapin breaks the integrity of SSH's secure channel. By carefully adjusting the sequence numbers during the handshake, an attacker can remove an arbitrary amount of messages sent by the client or server at the beginning of the secure channel without the client or server noticing it. ### Mitigations To mitigate this protocol vulnerability, OpenSSH suggested a so-called "strict kex" which alters the SSH handshake to ensure a Man-in-the-Middle attacker cannot introduce unauthenticated messages as well as convey sequence number manipulation across handshakes. **Warning: To take effect, both the client and server must support this countermeasure.** As a stop-gap measure, peers may also (temporarily) disable the affected algorithms and use unaffected alternatives like AES-GCM instead until patches are available. ### Details The SSH specifications of ChaCha20-Poly1305 (chacha20-poly1305@openssh.com) and Encrypt-then-MAC (*-etm@openssh.com MACs) are vulnerable against an arbitrary prefix truncation attack (a.k.a. Terrapin attack). This allows for an extension negotiation downgrade by stripping the SSH_MSG_EXT_INFO sent after the first message after SSH_MSG_NEWKEYS, downgrading security, and disabling attack countermeasures in some versions of OpenSSH. When targeting Encrypt-then-MAC, this attack requires the use of a CBC cipher to be practically exploitable due to the internal workings of the cipher mode. Additionally, this novel attack technique can be used to exploit previously unexploitable implementation flaws in a Man-in-the-Middle scenario. The attack works by an attacker injecting an arbitrary number of SSH_MSG_IGNORE messages during the initial key exchange and consequently removing the same number of messages just after the initial key exchange has concluded. This is possible due to missing authentication of the excess SSH_MSG_IGNORE messages and the fact that the implicit sequence numbers used within the SSH protocol are only checked after the initial key exchange. In the case of ChaCha20-Poly1305, the attack is guaranteed to work on every connection as this cipher does not maintain an internal state other than the message's sequence number. In the case of Encrypt-Then-MAC, practical exploitation requires the use of a CBC cipher; while theoretical integrity is broken for all ciphers when using this mode, message processing will fail at the application layer for CTR and stream ciphers. For more details see [https://terrapin-attack.com](https://terrapin-attack.com). ### Impact This attack targets the specification of ChaCha20-Poly1305 (chacha20-poly1305@openssh.com) and Encrypt-then-MAC (*-etm@openssh.com), which are widely adopted by well-known SSH implementations and can be considered de-facto standard. These algorithms can be practically exploited; however, in the case of Encrypt-Then-MAC, we additionally require the use of a CBC cipher. As a consequence, this attack works against all well-behaving SSH implementations supporting either of those algorithms and can be used to downgrade (but not fully strip) connection security in case SSH extension negotiation (RFC8308) is supported. The attack may also enable attackers to exploit certain implementation flaws in a man-in-the-middle (MitM) scenario.

  • ICSA-23-166-11Siemens SIMATIC S7-1500 TM MFP Linux Kernel2023-06-13icsa · cisa_csaf_otUS

    Multiple vulnerabilities have been identified in the additional GNU/Linux subsystem of the SIMATIC S7-1500 TM MFP V1.0. Siemens has released a new version for SIMATIC S7-1500 TM MFP - GNU/Linux subsystem and recommends to update to the latest version. This advisory lists vulnerabilities for firmware version V1.0 only; for V1.1 refer to Siemens Security Advisory SSA-265688 ( https://cert-portal.siemens.com/productcert/html/ssa-265688.html).

  • ICSA-24-193-11Siemens RUGGEDCOM APE 18082024-07-09icsa · cisa_csaf_otUS

    Palo Alto Networks has published [1] information on vulnerabilities in PAN-OS. This advisory lists the related Siemens Industrial products affected by these vulnerabilities. Siemens is preparing updates and recommends specific countermeasures for products where updates are not, or not yet available. Customers are advised to consult and implement the workarounds provided in Palo Alto Networks' upstream security notifications. [1] https://security.paloaltonetworks.com/

  • ICSA-24-319-08Siemens SINEC INS2024-11-12icsa · cisa_csaf_otUS

    SINEC INS before V1.0 SP2 Update 3 is affected by multiple vulnerabilities. Siemens has released a new version for SINEC INS and recommends to update to the latest version.

  • ICSA-25-044-09Siemens SCALANCE W700 IEEE 802.11ax2025-02-11icsa · cisa_csaf_otUS

    SCALANCE W-700 IEEE 802.11ax family devices are affected by multiple vulnerabilities. Siemens has released new versions for the affected products and recommends to update to the latest versions.

  • ICSA-25-105-08ABB M2M Gateway2025-04-07icsa · cisa_csaf_otUS

    ABB is aware of public reports of a vulnerabilities in product versions listed as affected in this advisory. An attacker who successfully exploited these vulnerabilities could cause the product to stop, make the product inacces-sible, take remote control of the product or insert and run arbitrary code. As part of ABB product lifecycle policy, once a product transitions to end-of-life, we discontinue maintenance, security patches, and technical support to focus on current and future technologies. While the product will continue to function, we strongly recommend implementing mitigations defined in this document, such as using a private APN cellular network between Arctic wireless gateways and ARM600 for establishing VPN tunnels, to mitigate security risks and avoid potential vulnerabilities. As part of ABB product lifecycle policy, once a product transitions to Limited state, we discontinue maintenance, security patches, and technical support to focus on current and future technologies. While the product will continue to function, we strongly recommend implementing mitigations defined in this document to mitigate security risks.

  • ICSA-25-162-05Siemens SIMATIC S7-1500 CPU family2025-06-10icsa · cisa_csaf_otUS

    Multiple vulnerabilities have been identified in the additional GNU/Linux subsystem of the firmware version V3.1.5 for the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP (incl. SIPLUS variant). Siemens is preparing fix versions and recommends countermeasures for products where fixes are not, or not yet available.

  • CGA-wvh7-h2xx-58522024-06-06vendor · osvUS
  • CGA-xx28-qv2j-6r3q2024-06-06vendor · osvUS
  • GO-2023-2402Man-in-the-middle attacker can compromise integrity of secure channel in golang.org/x/crypto2023-12-18vendor · osvUS

    A protocol weakness allows a MITM attacker to compromise the integrity of the secure channel before it is established, allowing the attacker to prevent transmission of a number of messages immediately after the secure channel is established without either side being aware. The impact of this attack is relatively limited, as it does not compromise confidentiality of the channel. Notably this attack would allow an attacker to prevent the transmission of the SSH2_MSG_EXT_INFO message, disabling a handful of newer security features. This protocol weakness was also fixed in OpenSSH 9.6.

  • PYSEC-2026-1758Prefix Truncation Attack against ChaCha20-Poly1305 and Encrypt-then-MAC aka Terrapin2026-07-07vendor · osvUS

    ### Summary Terrapin is a prefix truncation attack targeting the SSH protocol. More precisely, Terrapin breaks the integrity of SSH's secure channel. By carefully adjusting the sequence numbers during the handshake, an attacker can remove an arbitrary amount of messages sent by the client or server at the beginning of the secure channel without the client or server noticing it. ### Mitigations To mitigate this protocol vulnerability, OpenSSH suggested a so-called "strict kex" which alters the SSH handshake to ensure a Man-in-the-Middle attacker cannot introduce unauthenticated messages as well as convey sequence number manipulation across handshakes. **Warning: To take effect, both the client and server must support this countermeasure.** As a stop-gap measure, peers may also (temporarily) disable the affected algorithms and use unaffected alternatives like AES-GCM instead until patches are available. ### Details The SSH specifications of ChaCha20-Poly1305 (chacha20-poly1305@openssh.com) and Encrypt-then-MAC (*-etm@openssh.com MACs) are vulnerable against an arbitrary prefix truncation attack (a.k.a. Terrapin attack). This allows for an extension negotiation downgrade by stripping the SSH_MSG_EXT_INFO sent after the first message after SSH_MSG_NEWKEYS, downgrading security, and disabling attack countermeasures in some versions of OpenSSH. When targeting Encrypt-then-MAC, this attack requires the use of a CBC cipher to be practically exploitable due to the internal workings of the cipher mode. Additionally, this novel attack technique can be used to exploit previously unexploitable implementation flaws in a Man-in-the-Middle scenario. The attack works by an attacker injecting an arbitrary number of SSH_MSG_IGNORE messages during the initial key exchange and consequently removing the same number of messages just after the initial key exchange has concluded. This is possible due to missing authentication of the excess SSH_MSG_IGNORE messages and the fact that the implicit sequence numbers used within the SSH protocol are only checked after the initial key exchange. In the case of ChaCha20-Poly1305, the attack is guaranteed to work on every connection as this cipher does not maintain an internal state other than the message's sequence number. In the case of Encrypt-Then-MAC, practical exploitation requires the use of a CBC cipher; while theoretical integrity is broken for all ciphers when using this mode, message processing will fail at the application layer for CTR and stream ciphers. For more details see [https://terrapin-attack.com](https://terrapin-attack.com). ### Impact This attack targets the specification of ChaCha20-Poly1305 (chacha20-poly1305@openssh.com) and Encrypt-then-MAC (*-etm@openssh.com), which are widely adopted by well-known SSH implementations and can be considered de-facto standard. These algorithms can be practically exploited; however, in the case of Encrypt-Then-MAC, we additionally require the use of a CBC cipher. As a consequence, this attack works against all well-behaving SSH implementations supporting either of those algorithms and can be used to downgrade (but not fully strip) connection security in case SSH extension negotiation (RFC8308) is supported. The attack may also enable attackers to exploit certain implementation flaws in a man-in-the-middle (MitM) scenario.

08

auch bekannt als (11)

Weitere Namen und Kennungen dieser Entität.

09

quellen

Welche Quellen diesen Datensatz belegen und wann.

cnnvdenisa_euvdfstec_bduosvabb_psirtcert_bundcisa_csaf_otncsc_nlsick_psirtsiemens_psirtwago_psirtphoenix_contact_psirtNVDCVE.orgMITRE
veröffentlicht 2023-12-18geändert 2026-10-15
11

Referenzen (397)

Externe Belege — Patches, Meldungen, Analysen.

scry

Angreifer nutzen Schwachstellen wie diese gegen im Internet exponierte Dienste aus. Sehen Sie mit einem kostenlosen Passiv-Scan, was exponiert ist.

Kostenloser Scan