CVE-2023-23931MediumMicrosoft CVSS 6.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

Microsoft security update for CVE-2023-23931

Published
June 30, 2024
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-2023-23931. This page also shows what EchelonGraph holds for CVE-2023-23931, 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 products3

  • azl3 python-cryptography 3.3.2-5 on Azure Linux 3.0
  • cbl2 python-cryptography 3.3.2-4 on CBL Mariner 2.0
  • cm1 python-cryptography 3.3.2-2 on CBL Mariner 1.0

✅ Updates Microsoft lists: 3 updates

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

KB articleUpdateFixed build
—Security Update3.3.2-2
—Security Update3.3.2-4
—Security Update3.3.2-5

🧭 EchelonGraph on CVE-2023-23931

EchelonGraph score
6.5 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

cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. In affected versions `Cipher.update_into` would accept Python objects which implement the buffer protocol, but provide only immutable buffers. This would allow immutable objects (such as `bytes`) to be mutated, thus violating fundamental rules of Python and resulting in corrupted output. This now correctly raises an exception. This issue has been present since `update_into` was originally introduced in cryptography 1.8.

Published by GitHub, Inc., the CVE Numbering Authority that assigned CVE-2023-23931, 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)