CVE-2020-25657MediumMicrosoft CVSS 5.9CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Microsoft security update for CVE-2020-25657

Published
July 14, 2022
Last Modified
—

🔗 CVE IDs covered (1)

📋 Microsoft's advisory

EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2020-25657. This page also shows what EchelonGraph holds for CVE-2020-25657, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.

🎯 Affected products4

  • azl3 m2crypto 0.38.0-3 on Azure Linux 3.0
  • azl3 m2crypto 0.38.0-4 on Azure Linux 3.0
  • cbl2 m2crypto 0.38.0-3 on CBL Mariner 2.0
  • cm1 m2crypto 0.35.2-8 on CBL Mariner 1.0

✅ Updates Microsoft lists: 2 updates

2 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.

KB articleUpdateFixed build
—Security Update0.38.0-3
—Security Update0.35.2-8

🧭 EchelonGraph on CVE-2020-25657

EchelonGraph score
5.9 MEDIUM
CISA KEV
Not listed
Fix status
A fix is available — apply it.

Description from the CVE record (CVE.org), as published by its numbering authority

A flaw was found in all released versions of m2crypto, where they are vulnerable to Bleichenbacher timing attacks in the RSA decryption API via the timed processing of valid PKCS#1 v1.5 Ciphertext. The highest threat from this vulnerability is to confidentiality.

Published by Red Hat, Inc., the CVE Numbering Authority that assigned CVE-2020-25657, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).

🔗 References (2)