CVE-2023-52323: Medium severity PyCryptodome Pycryptodome Python vulnerability

Published Jan 5, 2024
·
Updated

PyCryptodome and pycryptodomex before 3.19.1 allow side-channel leakage for OAEP decryption, exploitable for a Manger attack.

Affected Software

9 affected componentsFixes available
debian/pycryptodome<=3.6.1-2, <=3.9.7+dfsg1-1, <=3.11.0+dfsg1-4, <=3.20.0+dfsg-1
ubuntu/pycryptodome<3.11.0+dfsg1-3ubuntu0.1
3.11.0+dfsg1-3ubuntu0.1
pip/pycryptodome<3.19.1
3.19.1
pip/pycryptodomex<3.19.1
3.19.1
PyCryptodome Pycryptodome Python<3.19.1
PyCryptodome Pycryptodomex Python<3.19.1
redhat/pycryptodome<3.19.1
3.19.1
IBM MQ Operator<=SC2: v3.2.0 - v3.2.13 CD:  v3.3.0, v3.4.0, v3.4.1, v3.5.0, v3.5.1 - v3.6.0 LTS: v2.0.0 - 2.0.29
IBM supplied MQ Advanced container images<=SC2: 9.4.0.6-r1, 9.4.0.6-r2, 9.4.0.7-r1, 9.4.0.10-r1, 9.4.0.10-r2, 9.4.0.11-r1, 9.4.0.11-r2, 9.4.0.11-r3CD: 9.4.1.0-r1, 9.4.1.0-r2, 9.4.1.1-r1, 9.4.2.0-r1, 9.4.2.0-r2, 9.4.2.1-r1, 9.4.2.1-r2, 9.4.3.0-r1LTS: 9.3.0.0-r1, 9.3.0.0-r2, 9.3.0.0-r3, 9.3.0.1-r1, 9.3.0.1-r2, 9.3.0.1-r3, 9.3.0.1-r4, 9.3.0.3-r1, 9.3.0.4-r1, 9.3.0.4-r2, 9.3.0.5-r1, 9.3.0.5-r2, 9.3.0.5-r3, 9.3.0.6-r1, 9.3.0.10-r1, 9.3.0.10-r2, 9.3.0.11-r1,9.3.0.11-r2, 9.3.0.15-r1, 9.3.0.16-r1, 9.3.0.16-r2, 9.3.0.17-r1, 9.3.0.17-r2, 9.3.0.17-r3, 9.3.0.20-r1, 9.3.0.20-r2, 9.3.0.21-r1, 9.3.0.21-r2, 9.3.0.21-r3, 9.3.0.25-r1, 9.4.0.0-r1, 9.4.0.0-r2, 9.4.0.0-r3, 9.4.0.5-r1, 9.4.0.5-r2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade ubuntu/pycryptodome to a version that resolves this vulnerability.

    Fixed in 3.11.0+dfsg1-3ubuntu0.1
  2. Upgrade

    Upgrade pip/pycryptodome to a version that resolves this vulnerability.

    Fixed in 3.19.1
  3. Upgrade

    Upgrade pip/pycryptodomex to a version that resolves this vulnerability.

    Fixed in 3.19.1
  4. Upgrade

    Upgrade redhat/pycryptodome to a version that resolves this vulnerability.

    Fixed in 3.19.1

Event History

Jan 5, 2024
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Advisory Published
via GitHub·06:30 AM
Jan 6, 2024
Data Sourced
via Red Hat·06:13 AM
DescriptionSeverityAffected Software
Jul 23, 2025
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2023-52323?

CVE-2023-52323 is rated as a high severity vulnerability due to its potential for side-channel attacks on OAEP decryption.

2

How do I fix CVE-2023-52323?

To fix CVE-2023-52323, upgrade PyCryptodome and pycryptodomex to version 3.19.1 or later.

3

What versions are affected by CVE-2023-52323?

CVE-2023-52323 affects all versions of PyCryptodome and pycryptodomex prior to 3.19.1.

4

What types of attacks can exploit CVE-2023-52323?

CVE-2023-52323 can be exploited through a Manger attack that takes advantage of side-channel leakage during OAEP decryption.

5

Is there a recommended action for users of PyCryptodome or pycryptodomex regarding CVE-2023-52323?

Users of PyCryptodome or pycryptodomex should immediately upgrade to version 3.19.1 to mitigate the risks associated with CVE-2023-52323.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203