Show filters
87 Total Results
Displaying 1-10 of 87
Sort by:
Attacker Value
Unknown
CVE-2019-25006
Disclosure Date: December 31, 2020 (last updated February 22, 2025)
An issue was discovered in the streebog crate before 0.8.0 for Rust. The Streebog hash function can produce the wrong answer.
0
Attacker Value
Unknown
CVE-2020-14254
Disclosure Date: December 16, 2020 (last updated February 22, 2025)
TLS-RSA cipher suites are not disabled in HCL BigFix Inventory up to v10.0.2. If TLS 2.0 and secure ciphers are not enabled then an attacker can passively record traffic and later decrypt it.
0
Attacker Value
Unknown
CVE-2020-25232
Disclosure Date: December 14, 2020 (last updated February 22, 2025)
A vulnerability has been identified in LOGO! 8 BM (incl. SIPLUS variants) (All versions < V8.3). Due to the usage of an insecure random number generation function and a deprecated cryptographic function, an attacker could extract the key that is used when communicating with an affected device on port 8080/tcp.
0
Attacker Value
Unknown
CVE-2020-25230
Disclosure Date: December 14, 2020 (last updated February 22, 2025)
A vulnerability has been identified in LOGO! 8 BM (incl. SIPLUS variants) (All versions < V8.3). Due to the usage of an outdated cipher mode on port 10005/tcp, an attacker could extract the encryption key from a captured communication with the device.
0
Attacker Value
Unknown
CVE-2020-28396
Disclosure Date: December 14, 2020 (last updated February 22, 2025)
A vulnerability has been identified in SICAM A8000 CP-8000 (All versions < V16), SICAM A8000 CP-8021 (All versions < V16), SICAM A8000 CP-8022 (All versions < V16). A web server misconfiguration of the affected device can cause insecure ciphers usage by a user´s browser. An attacker in a privileged position could decrypt the communication and compromise confidentiality and integrity of the transmitted information.
0
Attacker Value
Unknown
CVE-2020-7339
Disclosure Date: December 10, 2020 (last updated February 22, 2025)
Use of a Broken or Risky Cryptographic Algorithm vulnerability in McAfee Database Security Server and Sensor prior to 4.8.0 in the form of a SHA1 signed certificate that would allow an attacker on the same local network to potentially intercept communication between the Server and Sensors.
0
Attacker Value
Unknown
CVE-2020-4624
Disclosure Date: November 25, 2020 (last updated February 22, 2025)
IBM Cloud Pak for Security 1.3.0.1 (CP4S) uses weaker than expected cryptographic algorithms during negotiation could allow an attacker to decrypt sensitive information.
0
Attacker Value
Unknown
CVE-2020-29063
Disclosure Date: November 24, 2020 (last updated February 22, 2025)
An issue was discovered on CDATA 72408A, 9008A, 9016A, 92408A, 92416A, 9288, 97016, 97024P, 97028P, 97042P, 97084P, 97168P, FD1002S, FD1104, FD1104B, FD1104S, FD1104SN, FD1108S, FD1204S-R2, FD1204SN, FD1204SN-R2, FD1208S-R2, FD1216S-R1, FD1608GS, FD1608SN, FD1616GS, FD1616SN, and FD8000 devices. A custom encryption algorithm is used to store encrypted passwords. This algorithm will XOR the password with the hardcoded *j7a(L#yZ98sSd5HfSgGjMj8;Ss;d)(*&^#@$a2s0i3g value.
0
Attacker Value
Unknown
CVE-2020-4937
Disclosure Date: November 19, 2020 (last updated February 22, 2025)
IBM Sterling B2B Integrator Standard Edition 5.2.0.0 through 6.0.3.2 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. IBM X-Force ID: 191814.
0
Attacker Value
Unknown
CVE-2020-8897
Disclosure Date: November 16, 2020 (last updated February 22, 2025)
A weak robustness vulnerability exists in the AWS Encryption SDKs for Java, Python, C and Javalcript prior to versions 2.0.0. Due to the non-committing property of AES-GCM (and other AEAD ciphers such as AES-GCM-SIV or (X)ChaCha20Poly1305) used by the SDKs to encrypt messages, an attacker can craft a unique cyphertext which will decrypt to multiple different results, and becomes especially relevant in a multi-recipient setting. We recommend users update their SDK to 2.0.0 or later.
0