Vulnerabilities > CVE-2019-9836 - Use of a Broken or Risky Cryptographic Algorithm vulnerability in multiple products

047910
CVSS 5.0 - MEDIUM
Attack vector
NETWORK
Attack complexity
LOW
Privileges required
NONE
Confidentiality impact
PARTIAL
Integrity impact
NONE
Availability impact
NONE
network
low complexity
amd
opensuse
CWE-327
nessus

Summary

Secure Encrypted Virtualization (SEV) on Advanced Micro Devices (AMD) Platform Security Processor (PSP; aka AMD Secure Processor or AMD-SP) 0.17 build 11 and earlier has an insecure cryptographic implementation.

Common Attack Pattern Enumeration and Classification (CAPEC)

  • Encryption Brute Forcing
    An attacker, armed with the cipher text and the encryption algorithm used, performs an exhaustive (brute force) search on the key space to determine the key that decrypts the cipher text to obtain the plaintext.
  • Creating a Rogue Certificate Authority Certificate
    An attacker exploits a weakness in the MD5 hash algorithm (weak collision resistance) to generate a certificate signing request (CSR) that contains collision blocks in the "to be signed" part. The attacker specially crafts two different, but valid X.509 certificates that when hashed with the MD5 algorithm would yield the same value. The attacker then sends the CSR for one of the certificates to the Certification Authority which uses the MD5 hashing algorithm. That request is completely valid and the Certificate Authority issues an X.509 certificate to the attacker which is signed with its private key. An attacker then takes that signed blob and inserts it into another X.509 certificate that the attacker generated. Due to the MD5 collision, both certificates, though different, hash to the same value and so the signed blob works just as well in the second certificate. The net effect is that the attackers' second X.509 certificate, which the Certification Authority has never seen, is now signed and validated by that Certification Authority. To make the attack more interesting, the second certificate could be not just a regular certificate, but rather itself a signing certificate. Thus the attacker is able to start their own Certification Authority that is anchored in its root of trust in the legitimate Certification Authority that has signed the attackers' first X.509 certificate. If the original Certificate Authority was accepted by default by browsers, so will now the Certificate Authority set up by the attacker and of course any certificates that it signs. So the attacker is now able to generate any SSL certificates to impersonate any web server, and the user's browser will not issue any warning to the victim. This can be used to compromise HTTPS communications and other types of systems where PKI and X.509 certificates may be used (e.g., VPN, IPSec) .
  • Signature Spoof
    An attacker generates a message or datablock that causes the recipient to believe that the message or datablock was generated and cryptographically signed by an authoritative or reputable source, misleading a victim or victim operating system into performing malicious actions.
  • Cryptanalysis
    Cryptanalysis is a process of finding weaknesses in cryptographic algorithms and using these weaknesses to decipher the ciphertext without knowing the secret key (instance deduction). Sometimes the weakness is not in the cryptographic algorithm itself, but rather in how it is applied that makes cryptanalysis successful. An attacker may have other goals as well, such as: 1. Total Break - Finding the secret key 2. Global Deduction - Finding a functionally equivalent algorithm for encryption and decryption that does not require knowledge of the secret key. 3. Information Deduction - Gaining some information about plaintexts or ciphertexts that was not previously known 4. Distinguishing Algorithm - The attacker has the ability to distinguish the output of the encryption (ciphertext) from a random permutation of bits The goal of the attacker performing cryptanalysis will depend on the specific needs of the attacker in a given attack context. In most cases, if cryptanalysis is successful at all, an attacker will not be able to go past being able to deduce some information about the plaintext (goal 3). However, that may be sufficient for an attacker, depending on the context.

Nessus

NASL familySuSE Local Security Checks
NASL idOPENSUSE-2019-1770.NASL
descriptionThis update for kernel-firmware fixes the following issues : kernel-firmware was updated to version 20190618 : - cavium: Add firmware for CNN55XX crypto driver. - linux-firmware: Update firmware file for Intel Bluetooth 22161 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Update firmware file for Intel Bluetooth 9260 - linux-firmware: Update AMD SEV firmware (CVE-2019-9836, bsc#1139383) - linux-firmware: update licence text for Marvell firmware - linux-firmware: update firmware for mhdp8546 - linux-firmware: rsi: update firmware images for Redpine 9113 chipset - imx: sdma: update firmware to v3.5/v4.5 - nvidia: update GP10[2467] SEC2 RTOS with the one already used on GP108 - linux-firmware: Update firmware file for Intel Bluetooth 8265 - linux-firmware: Update firmware file for Intel Bluetooth 9260 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - amlogic: add video decoder firmwares - iwlwifi: update -46 firmwares for 22260 and 9000 series - iwlwifi: add firmware for 22260 and update 9000 series -46 firmwares - iwlwifi: add -46.ucode firmwares for 9000 series - amdgpu: update vega20 to the latest 19.10 firmware - amdgpu: update vega12 to the latest 19.10 firmware - amdgpu: update vega10 to the latest 19.10 firmware - amdgpu: update polaris11 to the latest 19.10 firmware - amdgpu: update polaris10 to the latest 19.10 firmware - amdgpu: update raven2 to the latest 19.10 firmware - amdgpu: update raven to the latest 19.10 firmware - amdgpu: update picasso to the latest 19.10 firmware - linux-firmware: update fw for qat devices - Mellanox: Add new mlxsw_spectrum firmware 13.2000.1122 - drm/i915/firmware: Add ICL HuC v8.4.3238 - drm/i915/firmware: Add ICL GuC v32.0.3 - drm/i915/firmware: Add GLK HuC v03.01.2893 - drm/i915/firmware: Add GLK GuC v32.0.3 - drm/i915/firmware: Add KBL GuC v32.0.3 - drm/i915/firmware: Add SKL GuC v32.0.3 - drm/i915/firmware: Add BXT GuC v32.0.3 - linux-firmware: Add firmware file for Intel Bluetooth 22161 - cxgb4: update firmware to revision 1.23.4.0 (bsc#1136334) - linux-firmware: Update NXP Management Complex firmware to version 10.14.3 - linux-firmware: add firmware for MT7615E - mediatek: update MT8173 VPU firmware to v1.1.2 [decoder] Enlarge struct vdec_pic_info to support more capture buffer plane and capture buffer format change. - linux-firmware: update Marvell 8797/8997 firmware images - nfp: update Agilio SmartNIC flower firmware to rev AOTC-2.10.A.23 This update was imported from the SUSE:SLE-15:Update update project.
last seen2020-06-01
modified2020-06-02
plugin id126903
published2019-07-22
reporterThis script is Copyright (C) 2019-2020 and is owned by Tenable, Inc. or an Affiliate thereof.
sourcehttps://www.tenable.com/plugins/nessus/126903
titleopenSUSE Security Update : kernel-firmware (openSUSE-2019-1770)