Back to vendor advisories
Microsoft Security Response CenterCVE-2006-5201

Multiple packages on Sun Solaris including (1) NSS; (2) Java JDK and JRE 5.0 Update 8 and earlier SDK and JRE 1.4.x up to 1.4.2_12 and SDK and JRE 1.3.x up to 1.3.1_19; (3) JSSE 1.0.3_03 and earlier; (4) IPSec/IKE; (5) Secure Global Desktop; and (6) StarOffice when using an RSA key with exponent 3 removes PKCS-1 padding before generating a hash which allows remote attackers to forge a PKCS #1 v1.5 signature that is signed by that RSA key and prevents these products from correctly verifying X.509 and other certificates that use PKCS #1.

Severity not listed 1 CVE Published Sep 25, 2020 at 12:00 AM UTC

Summary

Is Azure Linux the only Microsoft product that includes this open-source library and is therefore potentially affected by this vulnerability?

One of the main benefits to our customers who choose to use the Azure Linux distro is the commitment to keep it up to date with the most recent and most secure versions of the open source libraries with which the distro is composed. Microsoft is committed to transparency in this work which is why we began publishing CSAF/VEX in October 2025. See this blog post for more information.

If impact to additional products is identified, we will update the CVE to reflect this.

Products covered

  • nss-3.73-1.cm1.x86_64.rpm on CBL Mariner 1.0 x64

  • nss-devel-3.73-1.cm1.x86_64.rpm on CBL Mariner 1.0 x64

  • nss-libs-3.73-1.cm1.x86_64.rpm on CBL Mariner 1.0 x64

  • nss-debuginfo-3.73-1.cm1.x86_64.rpm on CBL Mariner 1.0 x64

  • nss-3.73-1.cm1.aarch64.rpm on CBL Mariner 1.0 ARM

  • nss-devel-3.73-1.cm1.aarch64.rpm on CBL Mariner 1.0 ARM

  • nss-libs-3.73-1.cm1.aarch64.rpm on CBL Mariner 1.0 ARM

  • nss-debuginfo-3.73-1.cm1.aarch64.rpm on CBL Mariner 1.0 ARM

Remediation

CBL-Mariner Releases

Vendor-listed fixes

  • 3.73-1

CVEs in this advisory 1

Updates

  1. Published by Microsoft Security Response Center

    The publication date reported by the vendor.

  2. Updated by Microsoft Security Response Center

    The vendor changed the advisory after it was first published.

  3. Added to SecurityAlert

    We collected the advisory from the official source.