py-cryptography -- allows programmers to misuse an APIentered 2023-04-10
no CVE referenced
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.
| Port | Package | Version | Status | Maintainer |
|---|---|---|---|---|
| security/py-cryptography-legacy | py312-cryptography-legacy | 3.4.8_3,1 | unaddressed | sunpoet@FreeBSD.org |
no CVE referenced
Range taken from the CVE record, check it before committing. make newentry in security/vuxml creates the vid.
<vuln vid="FIXME (make newentry)">
<topic>FIXME -- FIXME</topic>
<affects>
<package>
<name>py312-cryptography-legacy</name>
<range><lt>39.0.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>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.</p>
</body>
</description>
<references>
<cvename>CVE-2023-23931</cvename>
<url>https://nvd.nist.gov/vuln/detail/CVE-2023-23931</url>
</references>
<dates>
<discovery>2023-02-07</discovery>
<entry>2026-10-26</entry>
</dates>
</vuln>