Cbor2 5.6.0 fixes  issue that was causing a MemoryError when decoding large definite strings. It was due to the library attempting to allocate more memory than available, leading to a failure in memory allocation. The fix involves altering how the library manages memory allocation for large strings, thus preventing the MemoryError from being thrown and allowing the library to handle large strings correctly.
https://github.com/agronholm/cbor2/commit/387755eacf0be35591a478d3c67fe10618a6d542

Affected versions of the cbor2 package are vulnerable to Denial of Service (DoS) due to uncontrolled recursion when decoding deeply nested CBOR data. The cbor2.loads() function creates a CBORDecoder and calls decode(), which dispatches nested Array and Map values to recursive handlers such as decode_array and decode_map without an independent depth-tracking limit in cbor2/decoder.py and source/decoder.c.

Affected versions of the cbor2 package are vulnerable to Information Disclosure due to the CBORDecoder state being reused without clearing shareable values between decode operations. In cbor2, CBORDecoder.decode_from_bytes() and the CBORDecoder.fp setter (including the C extension _CBORDecoder_set_fp and the pure-Python cbor2/_decoder.py implementation) do not reset the internal shareables list that stores tag 28 (shareable) values for later retrieval via tag 29 (sharedref), allowing those references to persist across separate messages.

Affected versions of Cbor2 are vulnerable to Buffer Overflow. An attacker can crash a service using cbor2 to parse a CBOR binary by sending a long enough object.

Pycryptodome 3.20.0 addresses a vulnerability in the OAEP decryption process, which previously had a side-channel leakage issue. This vulnerability could potentially be exploited through a Manger attack, a type of cryptographic attack. The resolution of this issue enhances the security of the library, especially in its handling of OAEP decryption.
https://github.com/Legrandin/pycryptodome/commit/0deea1bfe1489e8c80d2053bbb06a1aa0b181ebd

Cbor2 5.6.0 fixes  issue that was causing a MemoryError when decoding large definite strings. It was due to the library attempting to allocate more memory than available, leading to a failure in memory allocation. The fix involves altering how the library manages memory allocation for large strings, thus preventing the MemoryError from being thrown and allowing the library to handle large strings correctly.
https://github.com/agronholm/cbor2/commit/387755eacf0be35591a478d3c67fe10618a6d542

Affected versions of the cbor2 package are vulnerable to Denial of Service (DoS) due to uncontrolled recursion when decoding deeply nested CBOR data. The cbor2.loads() function creates a CBORDecoder and calls decode(), which dispatches nested Array and Map values to recursive handlers such as decode_array and decode_map without an independent depth-tracking limit in cbor2/decoder.py and source/decoder.c.

Affected versions of the cbor2 package are vulnerable to Information Disclosure due to the CBORDecoder state being reused without clearing shareable values between decode operations. In cbor2, CBORDecoder.decode_from_bytes() and the CBORDecoder.fp setter (including the C extension _CBORDecoder_set_fp and the pure-Python cbor2/_decoder.py implementation) do not reset the internal shareables list that stores tag 28 (shareable) values for later retrieval via tag 29 (sharedref), allowing those references to persist across separate messages.

Affected versions of Cbor2 are vulnerable to Buffer Overflow. An attacker can crash a service using cbor2 to parse a CBOR binary by sending a long enough object.

Pycryptodome 3.20.0 addresses a vulnerability in the OAEP decryption process, which previously had a side-channel leakage issue. This vulnerability could potentially be exploited through a Manger attack, a type of cryptographic attack. The resolution of this issue enhances the security of the library, especially in its handling of OAEP decryption.
https://github.com/Legrandin/pycryptodome/commit/0deea1bfe1489e8c80d2053bbb06a1aa0b181ebd

Cbor2 5.6.0 fixes  issue that was causing a MemoryError when decoding large definite strings. It was due to the library attempting to allocate more memory than available, leading to a failure in memory allocation. The fix involves altering how the library manages memory allocation for large strings, thus preventing the MemoryError from being thrown and allowing the library to handle large strings correctly.
https://github.com/agronholm/cbor2/commit/387755eacf0be35591a478d3c67fe10618a6d542

Affected versions of the cbor2 package are vulnerable to Denial of Service (DoS) due to uncontrolled recursion when decoding deeply nested CBOR data. The cbor2.loads() function creates a CBORDecoder and calls decode(), which dispatches nested Array and Map values to recursive handlers such as decode_array and decode_map without an independent depth-tracking limit in cbor2/decoder.py and source/decoder.c.

Affected versions of the cbor2 package are vulnerable to Information Disclosure due to the CBORDecoder state being reused without clearing shareable values between decode operations. In cbor2, CBORDecoder.decode_from_bytes() and the CBORDecoder.fp setter (including the C extension _CBORDecoder_set_fp and the pure-Python cbor2/_decoder.py implementation) do not reset the internal shareables list that stores tag 28 (shareable) values for later retrieval via tag 29 (sharedref), allowing those references to persist across separate messages.

Affected versions of Cbor2 are vulnerable to Buffer Overflow. An attacker can crash a service using cbor2 to parse a CBOR binary by sending a long enough object.

Pycryptodome 3.20.0 addresses a vulnerability in the OAEP decryption process, which previously had a side-channel leakage issue. This vulnerability could potentially be exploited through a Manger attack, a type of cryptographic attack. The resolution of this issue enhances the security of the library, especially in its handling of OAEP decryption.
https://github.com/Legrandin/pycryptodome/commit/0deea1bfe1489e8c80d2053bbb06a1aa0b181ebd

Cbor2 5.6.0 fixes  issue that was causing a MemoryError when decoding large definite strings. It was due to the library attempting to allocate more memory than available, leading to a failure in memory allocation. The fix involves altering how the library manages memory allocation for large strings, thus preventing the MemoryError from being thrown and allowing the library to handle large strings correctly.
https://github.com/agronholm/cbor2/commit/387755eacf0be35591a478d3c67fe10618a6d542

Affected versions of the cbor2 package are vulnerable to Denial of Service (DoS) due to uncontrolled recursion when decoding deeply nested CBOR data. The cbor2.loads() function creates a CBORDecoder and calls decode(), which dispatches nested Array and Map values to recursive handlers such as decode_array and decode_map without an independent depth-tracking limit in cbor2/decoder.py and source/decoder.c.

Affected versions of the cbor2 package are vulnerable to Information Disclosure due to the CBORDecoder state being reused without clearing shareable values between decode operations. In cbor2, CBORDecoder.decode_from_bytes() and the CBORDecoder.fp setter (including the C extension _CBORDecoder_set_fp and the pure-Python cbor2/_decoder.py implementation) do not reset the internal shareables list that stores tag 28 (shareable) values for later retrieval via tag 29 (sharedref), allowing those references to persist across separate messages.

Affected versions of Cbor2 are vulnerable to Buffer Overflow. An attacker can crash a service using cbor2 to parse a CBOR binary by sending a long enough object.

Pycryptodome 3.20.0 addresses a vulnerability in the OAEP decryption process, which previously had a side-channel leakage issue. This vulnerability could potentially be exploited through a Manger attack, a type of cryptographic attack. The resolution of this issue enhances the security of the library, especially in its handling of OAEP decryption.
https://github.com/Legrandin/pycryptodome/commit/0deea1bfe1489e8c80d2053bbb06a1aa0b181ebd

Pycryptodome 3.20.0 addresses a vulnerability in the OAEP decryption process, which previously had a side-channel leakage issue. This vulnerability could potentially be exploited through a Manger attack, a type of cryptographic attack. The resolution of this issue enhances the security of the library, especially in its handling of OAEP decryption.
https://github.com/Legrandin/pycryptodome/commit/0deea1bfe1489e8c80d2053bbb06a1aa0b181ebd

Pycryptodome 3.20.0 addresses a vulnerability in the OAEP decryption process, which previously had a side-channel leakage issue. This vulnerability could potentially be exploited through a Manger attack, a type of cryptographic attack. The resolution of this issue enhances the security of the library, especially in its handling of OAEP decryption.
https://github.com/Legrandin/pycryptodome/commit/0deea1bfe1489e8c80d2053bbb06a1aa0b181ebd

Pycryptodome 3.20.0 addresses a vulnerability in the OAEP decryption process, which previously had a side-channel leakage issue. This vulnerability could potentially be exploited through a Manger attack, a type of cryptographic attack. The resolution of this issue enhances the security of the library, especially in its handling of OAEP decryption.
https://github.com/Legrandin/pycryptodome/commit/0deea1bfe1489e8c80d2053bbb06a1aa0b181ebd

Pycryptodome 3.20.0 addresses a vulnerability in the OAEP decryption process, which previously had a side-channel leakage issue. This vulnerability could potentially be exploited through a Manger attack, a type of cryptographic attack. The resolution of this issue enhances the security of the library, especially in its handling of OAEP decryption.
https://github.com/Legrandin/pycryptodome/commit/0deea1bfe1489e8c80d2053bbb06a1aa0b181ebd