3912 matches found
Mitsubishi Electric Europe B.V. smartRTU and INEA ME-RTU
1. EXECUTIVE SUMMARY CVSS v3 9.8 ATTENTION: Exploitable remotely/low attack complexity Vendor: Mitsubishi Electric Europe B.V. Equipment: smartRTU and INEA ME-RTU Vulnerabilities: OS Command Injection, Improper Access Control, Cross-site Scripting, Use of Hard-coded Credentials, Unprotected...
ECOA Building Automation System Hard-coded Credentials SSH Access
Summary 1 The Risk-Terminator Web Graphic control BEMS Building Energy Management System are designed to provide you with the latest in the Human Machine Interface HMI technology, for completely monitoring and controlling management. It may be used singly for small and medium sized facilities,...
CVE-2021-34571
Multiple Wireless M-Bus devices by Enbra use Hard-coded Credentials in Security mode 5 without an option to change the encryption key. An adversary can learn all information that is available in Enbra EWM...
CVE-2021-34565
In PEPPERL+FUCHS WirelessHART-Gateway 3.0.7 to 3.0.9 the SSH and telnet services are active with hard-coded credentials...
CVE-2021-34565
In PEPPERL+FUCHS WirelessHART-Gateway 3.0.7 to 3.0.9 the SSH and telnet services are active with hard-coded credentials...
CVE-2021-34565 In WirelessHART-Gateway versions 3.0.7 to 3.0.9 hard-coded credentials have been found
In PEPPERL+FUCHS WirelessHART-Gateway 3.0.7 to 3.0.9 the SSH and telnet services are active with hard-coded credentials...
CVE-2021-34565
The CVE-2021-34565 vulnerability affects Pepperl+Fuchs WirelessHART-Gateway versions 3.0.7–3.0.9, where SSH and Telnet services run with hard-coded credentials. This is reported with high impact: remote access to the gateway could be obtained (CVSS v3.1 base score 9.8). Public advisories (ICS/CIS...
IBM Sterling Secure Proxy Hardcoded Credentials Vulnerability
IBM Sterling Secure Proxy creates a security barrier for trusted networks by preventing direct connections between external partners and internal servers. IBM Sterling Secure Proxy versions 6.0.1, 6.0.2, 2.4.3.2, and 3.4.3.2 contain a hard-coded credential vulnerability. An attacker could use thi...
Pepperl Fuchs WirelessHART-Gateway 信任管理问题漏洞
The Pepperl Fuchs WirelessHART-Gateway is a gateway device from Pepperl Fuchs, Germany. A trust management issue vulnerability exists in Pepperl Fuchs WirelessHART-Gateway versions 3.0.7 through 3.0.9, which arises when SSH and telnet services are active using hard-coded credentials...
PT-2021-20550 · Pepperl+Fuchs · Wirelesshart Gateway
Name of the Vulnerable Software and Affected Versions: PEPPERL+FUCHS WirelessHART-Gateway versions 3.0.7 through 3.0.9 Description: The issue concerns hard-coded credentials in the SSH and telnet services of the affected device. Recommendations: For versions 3.0.7 through 3.0.9, consider disablin...
CVE-2021-29728
IBM Sterling Secure Proxy 6.0.1, 6.0.2, 2.4.3.2, and 3.4.3.2 contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. IBM X-Force ID: 201160...
CVE-2021-29728
IBM Sterling Secure Proxy 6.0.1, 6.0.2, 2.4.3.2, and 3.4.3.2 contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. IBM X-Force ID: 201160...
CVE-2021-29728
IBM Sterling Secure Proxy 6.0.1, 6.0.2, 2.4.3.2, and 3.4.3.2 contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. IBM X-Force ID: 201160...
CVE-2021-29728
CVE-2021-29728 affects IBM Sterling Secure Proxy/Sterling Proxy components. The connected documents confirm hard-coded credentials (passwords or keys) used for inbound authentication, outbound communication, or internal data encryption in versions 6.0.1, 6.0.2, 2.4.3.2, and 3.4.3.2. Implications ...
IBM Sterling Secure Proxy 信任管理问题漏洞
IBM Sterling Secure Proxy creates a security barrier for trusted networks by preventing direct connections between external partners and internal servers. IBM Sterling Secure Proxy versions 6.0.1, 6.0.2, 2.4.3.2, and 3.4.3.2 contain a hard-coded credential vulnerability. An attacker could use thi...
PT-2021-18435 · Ibm · Ibm Sterling Secure Proxy
Name of the Vulnerable Software and Affected Versions: IBM Sterling Secure Proxy versions 2.4.3.2, 3.4.3.2, 6.0.1, 6.0.2 Description: The issue concerns hard-coded credentials, such as a password or cryptographic key, used for inbound authentication, outbound communication to external components,...
Security Bulletin: Multiple Vulnerabilities Affect IBM Secure External Authentication Server
Summary There are multiple vulnerabilities in IBM Secure External Authentication Server. IBM Secure External Authentication Server has addressed the applicable CVEs. Vulnerability Details CVEID: CVE-2021-29722 DESCRIPTION: IBM Sterling Secure Proxy uses weaker than expected cryptographic algorith...
Security Bulletin: Multiple Vulnerabilities Affect IBM Secure Proxy
Summary There are multiple vulnerabilities in IBM Secure Proxy. IBM Secure Proxy has addressed the applicable CVEs. Vulnerability Details CVEID: CVE-2021-29723 DESCRIPTION: IBM Sterling Secure Proxy uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly...
D-Link DSR-500N Default Account Vulnerability
A security vulnerability exists in the D-Link DSR-500N, a wireless router from D-Link, Taiwan, China, which stems from the fact that version 1.02 of the D-Link DSR-500N contains hard-coded credentials for user accounts that are not documented in the "etc/passwd" file. The vulnerability is caused ...
D-Link DVG-3104MS Default Account Vulnerability
A security vulnerability exists in D-Link DVG-3104MS, a gateway from D-Link, Taiwan, China, due to the fact that D-Link DVG-3104MS versions 1.0.2.0.3, 1.0.2.0.4 and 1.0.2.0.4E contain " /etc/passwd" file that does not record hard-coded credentials for user accounts. An attacker could exploit this...