Most recent entries from all

BREW-azure-cli-CVE-2023-23931 — Cipher.update_into can corrupt memory if passed an immutable python object as the outbuf

2026-10-02T16:52:58.368184+00:00

Affected: Homebrew: azure-cli

Previously, `Cipher.update_into` would accept Python objects which implement the buffer protocol, but provide only immutable buffers:

```pycon >>> outbuf = b"\x00" * 32 >>> c = ciphers.Cipher(AES(b"\x00" * 32), modes.ECB()).encryptor() >>> c.update_into(b"\x00" * 16, outbuf) 16 >>> outbuf b'\xdc\x95\xc0x\xa2@\x89\x89\xadH\xa2\x14\x92\x84 \x87\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00' ```

This would allow immutable objects (such as `bytes`) to be mutated, thus violating fundamental rules of Python. This is a soundness bug -- it allows programmers to misuse an API, it cannot be exploited by attacker controlled data alone.

This now correctly raises an exception.

This issue has been present since `update_into` was originally introduced in cryptography 1.8.

CVE-2023-23931 — Cipher.update_into can corrupt memory in pyca cryptography

2026-10-02T16:52:58.368238+00:00

Affected: pyca cryptography

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.

GHSA-w7pp-m8wf-vj6r — Cipher.update_into can corrupt memory if passed an immutable python object as the outbuf

2026-10-02T16:52:58.368275+00:00

Affected: PyPI: cryptography

Previously, `Cipher.update_into` would accept Python objects which implement the buffer protocol, but provide only immutable buffers:

This now correctly raises an exception.

This issue has been present since `update_into` was originally introduced in cryptography 1.8.