← Back
CWE-321

308 CVEs • Abstraction: Variant • Likelihood of Exploit: High

Use of Hard-coded Cryptographic Key

The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered.

JSON object

Loading...

CVEs (308)

CVE
VENDORS
PRODUCTS
UPDATED
PUBLISHED
CVSS
2Gravitl
Netmaker
2Netmaker
Netmaker
Jun 17, 2026
Feb 18, 2022
N/A· v4
9.8 CRITICAL· v3
10.0 HIGH· v2
Use of Hard-coded Cryptographic Key in Go github.com/gravitl/netmaker prior to 0.8.5,0.9.4,0.10.0,0.10.1.
1Advantech
1Adam 3600 Firmware
Jun 17, 2026
Feb 4, 2022
N/A· v4
9.8 CRITICAL· v3
7.5 HIGH· v2
The affected product has a hardcoded private key available inside the project folder, which may allow an attacker to achieve Web Server login and perform further actions.
1Reolink
1Rlc 410w Firmware
Jun 17, 2026
Jan 28, 2022
N/A· v4
5.9 MEDIUM· v3
4.3 MEDIUM· v2
An information disclosure vulnerability exists due to the hardcoded TLS key of reolink RLC-410W v3.0.0.136_20121102. A specially-crafted man-in-the-middle attack can lead to a disclosure of sensitive information. An atta...Show more
An information disclosure vulnerability exists due to the hardcoded TLS key of reolink RLC-410W v3.0.0.136_20121102. A specially-crafted man-in-the-middle attack can lead to a disclosure of sensitive information. An attacker can perform a man-in-the-middle attack to trigger this vulnerability.Show less
1Bosch
4Access Management System
Access Professional EditionAmc2 Firmware+1 more
Jun 17, 2026
Jan 19, 2022
N/A· v4
7.1 HIGH· v3
3.6 LOW· v2
Communication to the AMC2 uses a state-of-the-art cryptographic algorithm for symmetric encryption called Blowfish. An attacker could retrieve the key from the firmware to decrypt network traffic between the AMC2 and the...Show more
Communication to the AMC2 uses a state-of-the-art cryptographic algorithm for symmetric encryption called Blowfish. An attacker could retrieve the key from the firmware to decrypt network traffic between the AMC2 and the host system. Thus, an attacker can exploit this vulnerability to decrypt and modify network traffic, decrypt and further investigate the device\'s firmware file, and change the device configuration. The attacker needs to have access to the local network, typically even the same subnet.Show less
1Philips
1Patient Information Center Ix
Jun 17, 2026
Dec 27, 2021
N/A· v4
5.5 MEDIUM· v3
2.1 LOW· v2
The use of a hard-coded cryptographic key significantly increases the possibility encrypted data may be recovered from the Patient Information Center iX (PIC iX) Versions B.02, C.02, and C.03.
1Dell
1Powerpath Management Appliance
Jun 17, 2026
Dec 21, 2021
N/A· v4
6.7 MEDIUM· v3
7.2 HIGH· v2
Dell PowerPath Management Appliance, versions 3.2, 3.1, 3.0 P01, 3.0, and 2.6, use hard-coded cryptographic key. A local high-privileged malicious user may potentially exploit this vulnerability to gain access to secrets...Show more
Dell PowerPath Management Appliance, versions 3.2, 3.1, 3.0 P01, 3.0, and 2.6, use hard-coded cryptographic key. A local high-privileged malicious user may potentially exploit this vulnerability to gain access to secrets and elevate to gain higher privileges.Show less
1Cisco
1Policy Suite
Jun 17, 2026
Nov 4, 2021
N/A· v4
9.8 CRITICAL· v3
10.0 HIGH· v2
A vulnerability in the key-based SSH authentication mechanism of Cisco Policy Suite could allow an unauthenticated, remote attacker to log in to an affected system as the root user. This vulnerability is due to the re-us...Show more
A vulnerability in the key-based SSH authentication mechanism of Cisco Policy Suite could allow an unauthenticated, remote attacker to log in to an affected system as the root user. This vulnerability is due to the re-use of static SSH keys across installations. An attacker could exploit this vulnerability by extracting a key from a system under their control. A successful exploit could allow the attacker to log in to an affected system as the root user.Show less
1Auvesy
1Versiondog
Jun 17, 2026
Oct 22, 2021
N/A· v4
8.2 HIGH· v3
6.4 MEDIUM· v2
The affected product uses a hard-coded blowfish key for encryption/decryption processes. The key can be easily extracted from binaries.
1Qsan
1Storage Manager
Jun 17, 2026
Jul 7, 2021
N/A· v4
9.8 CRITICAL· v3
7.5 HIGH· v2
Use of hard-coded cryptographic key vulnerability in QSAN Storage Manager allows attackers to obtain users’ credentials and related permissions. Suggest contacting with QSAN and refer to recommendations in QSAN Document.
1Zoll
1Defibrillator Dashboard
Jun 17, 2026
Jun 16, 2021
N/A· v4
5.5 MEDIUM· v3
2.1 LOW· v2
ZOLL Defibrillator Dashboard, v prior to 2.2, The affected products utilize an encryption key in the data exchange process, which is hardcoded. This could allow an attacker to gain access to sensitive information.
1Siemens
1Siveillance Video Open Network Bridge
Jun 17, 2026
Apr 22, 2021
N/A· v4
8.8 HIGH· v3
4.0 MEDIUM· v2
A vulnerability has been identified in Siveillance Video Open Network Bridge (2020 R3), Siveillance Video Open Network Bridge (2020 R2), Siveillance Video Open Network Bridge (2020 R1), Siveillance Video Open Network Bri...Show more
A vulnerability has been identified in Siveillance Video Open Network Bridge (2020 R3), Siveillance Video Open Network Bridge (2020 R2), Siveillance Video Open Network Bridge (2020 R1), Siveillance Video Open Network Bridge (2019 R3), Siveillance Video Open Network Bridge (2019 R2), Siveillance Video Open Network Bridge (2019 R1), Siveillance Video Open Network Bridge (2018 R3), Siveillance Video Open Network Bridge (2018 R2). Affected Open Network Bridges store user credentials for the authentication between ONVIF clients and ONVIF server using a hard-coded key. The encrypted credentials can be retrieved via the MIP SDK. This could allow an authenticated remote attacker to retrieve and decrypt all credentials stored on the ONVIF server.Show less
1Siemens
2Opcenter Quality
Qms Automotive
Jun 17, 2026
Apr 22, 2021
N/A· v4
9.8 CRITICAL· v3
7.5 HIGH· v2
A vulnerability has been identified in Opcenter Quality (All versions < V12.2), QMS Automotive (All versions < V12.30). A private sign key is shipped with the product without adequate protection.
1Juniper
1Junos
Jun 17, 2026
Apr 22, 2021
N/A· v4
9.8 CRITICAL· v3
7.5 HIGH· v2
The use of multiple hard-coded cryptographic keys in cSRX Series software in Juniper Networks Junos OS allows an attacker to take control of any instance of a cSRX deployment through device management services. This issu...Show more
The use of multiple hard-coded cryptographic keys in cSRX Series software in Juniper Networks Junos OS allows an attacker to take control of any instance of a cSRX deployment through device management services. This issue affects: Juniper Networks Junos OS on cSRX Series: All versions prior to 20.2R3; 20.3 versions prior to 20.3R2; 20.4 versions prior to 20.4R2.Show less
1Cnesty
1Helpcom
Jun 17, 2026
Feb 24, 2021
N/A· v4
8.8 HIGH· v3
6.8 MEDIUM· v2
Helpcom before v10.0 contains a file download and execution vulnerability caused by storing hardcoded cryptographic key. It finally leads to a file download and execution via access to crafted web page.
1Reolink
7Rlc 410 Firmware
Rlc 422 FirmwareRlc 423 Firmware+4 more
Jun 17, 2026
Jan 26, 2021
N/A· v4
7.8 HIGH· v3
4.6 MEDIUM· v2
An attacker with local network access can obtain a fixed cryptography key which may allow for further compromise of Reolink P2P cameras outside of local network access
1Siemens
8Scalance Xr324 12m Firmware
Scalance Xr324 12m Ts FirmwareScalance Xr324 4m Eec Firmware+5 more
Jun 17, 2026
Jan 12, 2021
N/A· v4
5.9 MEDIUM· v3
4.3 MEDIUM· v2
A vulnerability has been identified in SCALANCE X-200RNA switch family (All versions < V3.2.7), SCALANCE X-300 switch family (incl. X408 and SIPLUS NET variants) (All versions < V4.1.0). Devices do not create a new uniqu...Show more
A vulnerability has been identified in SCALANCE X-200RNA switch family (All versions < V3.2.7), SCALANCE X-300 switch family (incl. X408 and SIPLUS NET variants) (All versions < V4.1.0). Devices do not create a new unique private key after factory reset. An attacker could leverage this situation to a man-in-the-middle situation and decrypt previously captured traffic.Show less
1Siemens
65Scalance X200 4pirt Firmware
Scalance X201 3pirt FirmwareScalance X202 2irt Firmware+62 more
Jun 17, 2026
Jan 12, 2021
N/A· v4
5.9 MEDIUM· v3
4.3 MEDIUM· v2
A vulnerability has been identified in SCALANCE X-200 switch family (incl. SIPLUS NET variants) (All versions < V5.2.5), SCALANCE X-200IRT switch family (incl. SIPLUS NET variants) (All versions < V5.5.0), SCALANCE X-200...Show more
A vulnerability has been identified in SCALANCE X-200 switch family (incl. SIPLUS NET variants) (All versions < V5.2.5), SCALANCE X-200IRT switch family (incl. SIPLUS NET variants) (All versions < V5.5.0), SCALANCE X-200RNA switch family (All versions < V3.2.7). Devices create a new unique key upon factory reset, except when used with C-PLUG. When used with C-PLUG the devices use the hardcoded private RSA-key shipped with the firmware-image. An attacker could leverage this situation to a man-in-the-middle situation and decrypt previously captured traffic.Show less
1Siemens
1Logo! 8 Bm Firmware
Jun 17, 2026
Dec 14, 2020
N/A· v4
7.7 HIGH· v3
3.6 LOW· v2
A vulnerability has been identified in LOGO! 8 BM (incl. SIPLUS variants) (All versions < V8.3), LOGO! Soft Comfort (All versions < V8.3). The LOGO! program files generated and used by the affected components offer the p...Show more
A vulnerability has been identified in LOGO! 8 BM (incl. SIPLUS variants) (All versions < V8.3), LOGO! Soft Comfort (All versions < V8.3). The LOGO! program files generated and used by the affected components offer the possibility to save user-defined functions (UDF) in a password protected way. This protection is implemented in the software that displays the information. An attacker could reverse engineer the UDFs directly from stored program files.Show less
1Siemens
1Logo! 8 Bm Firmware
Jun 17, 2026
Dec 14, 2020
N/A· v4
5.5 MEDIUM· v3
2.1 LOW· v2
A vulnerability has been identified in LOGO! 8 BM (incl. SIPLUS variants) (All versions < V8.3). The firmware update of affected devices contains the private RSA key that is used as a basis for encryption of communicatio...Show more
A vulnerability has been identified in LOGO! 8 BM (incl. SIPLUS variants) (All versions < V8.3). The firmware update of affected devices contains the private RSA key that is used as a basis for encryption of communication with the device.Show less
1Siemens
2Logo! 8 Bm Firmware
Logo! Soft Comfort
Jun 17, 2026
Dec 14, 2020
N/A· v4
5.5 MEDIUM· v3
2.1 LOW· v2
A vulnerability has been identified in LOGO! 8 BM (incl. SIPLUS variants) (All versions < V8.3), LOGO! Soft Comfort (All versions < V8.3). The encryption of program data for the affected devices uses a static key. An att...Show more
A vulnerability has been identified in LOGO! 8 BM (incl. SIPLUS variants) (All versions < V8.3), LOGO! Soft Comfort (All versions < V8.3). The encryption of program data for the affected devices uses a static key. An attacker could use this key to extract confidential information from protected program files.Show less