# CVE-2023-52323: PyCryptodome and pycryptodomex side-channel leakage for OAEP decryption

> Attackers can exploit side-channel leakage in OAEP decryption to recover plaintext, affecting applications using PyCryptodome.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Jan 2024
- **Updated:** 3 Jun 2025
- **Also known as:** DEBIAN-CVE-2023-52323, ECHO-6224-38b9-b98e, GHSA-j225-cvw7-qrx7, OESA-2024-1046, OESA-2024-1053, OESA-2024-2146, OESA-2024-2147, OESA-2024-2148, OESA-2024-2149, PYSEC-2024-3, PYSEC-2026-1811, SUSE-RU-2024:1829-1, SUSE-RU-2024:1829-2, SUSE-SU-2024:0557-1, SUSE-SU-2024:0585-1, SUSE-SU-2024:0601-1, UBUNTU-CVE-2023-52323, USN-6595-1, openSUSE-SU-2024:13567-1, openSUSE-SU-2024:13568-1, openSUSE-SU-2026:12028-1, openSUSE-SU-2026:12029-1

## What is CVE-2023-52323?

CVE-2023-52323 is a medium-severity vulnerability in n/a, published on 5 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-203 (Observable Discrepancy)

## Which versions are affected by CVE-2023-52323?

6 open source packages ship an affected version, including pycryptodome and pycryptodomex. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pycryptodome` | PyPI | All versions | 3.19.1 |
| `pycryptodome` | PyPI | All versions | 3.19.1 |
| `pycryptodome` | PyPI | All versions | 3.19.1 |
| `pycryptodomex` | PyPI | All versions | 3.19.1 |
| `pycryptodomex` | PyPI | All versions | 3.19.1 |
| `pycryptodomex` | PyPI | All versions | 3.19.1 |
| `python-pycryptodomex` | SUSE:Enterprise Storage 7.1 | All versions | 3.9.9-150300.3.3.1 |
| `python-pycryptodome` | SUSE:Linux Enterprise Module for Basesystem 15 SP5 | All versions | 3.9.0-150200.9.1 |
| `python-pycryptodomex` | SUSE:Linux Enterprise Module for Package Hub 15 SP5 | All versions | 3.9.9-150300.3.3.1 |
| `python-pycryptodome` | SUSE:Linux Enterprise Module for Public Cloud 15 SP2 | All versions | 3.9.0-150100.3.6.1 |
| `python-aliyun-python-sdk` | SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | All versions | 1.0.0-150400.10.3.1 |
| `python-aliyun-python-sdk-aas` | SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | All versions | 2.1.1-150400.10.3.1 |
| `python-aliyun-python-sdk-acm` | SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | All versions | 1.0.1-150400.10.3.1 |
| `python-aliyun-python-sdk-acms-open` | SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | All versions | 1.0.0-150400.10.3.1 |
| `python-aliyun-python-sdk-actiontrail` | SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | All versions | 2.2.0-150400.10.3.1 |
| `python-aliyun-python-sdk-adb` | SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | All versions | 1.1.10-150400.10.3.1 |
| `python-aliyun-python-sdk-adcp` | SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | All versions | 1.0.0-150400.9.3.1 |
| `python-aliyun-python-sdk-address-purification` | SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | All versions | 1.0.1-150400.10.3.1 |
| `python-aliyun-python-sdk-aegis` | SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | All versions | 1.0.6-150400.10.3.1 |
| `python-aliyun-python-sdk-afs` | SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | All versions | 1.0.1-150400.10.3.1 |
| `python-aliyun-python-sdk-aigen` | SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | All versions | 1.0.0-150400.9.3.1 |
| `python-aliyun-python-sdk-aimiaobi` | SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | All versions | 1.0.0-150400.9.3.1 |
| `python-aliyun-python-sdk-airec` | SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | All versions | 2.1.0-150400.10.3.1 |
| `python-aliyun-python-sdk-airticketopen` | SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | All versions | 3.0.3-150400.9.3.1 |
| `python-aliyun-python-sdk-alb` | SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | All versions | 1.0.16-150400.9.3.1 |
| `python-aliyun-python-sdk-alidns` | SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | All versions | 3.0.7-150400.10.3.1 |
| `python-aliyun-python-sdk-aligreen-console` | SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | All versions | 1.0.3-150400.10.3.1 |
| `python-aliyun-python-sdk-alikafka` | SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | All versions | 1.0.6-150400.9.3.1 |
| `python-aliyun-python-sdk-alimt` | SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | All versions | 3.2.0-150400.10.3.1 |
| `python-aliyun-python-sdk-alinlp` | SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | All versions | 1.0.24-150400.10.3.1 |
| `python-aliyun-python-sdk-aliyuncvc` | SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | All versions | 1.0.10.2-150400.10.3.1 |
| `python-aliyun-python-sdk-amptest` | SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | All versions | 1.0.0-150400.9.3.1 |
| `python-aliyun-python-sdk-amqp-open` | SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | All versions | 1.1.4-150400.10.3.1 |
| `python-aliyun-python-sdk-antiddos-public` | SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | All versions | 2.0.4-150400.9.3.1 |
| `python-aliyun-python-sdk-apds` | SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | All versions | 1.0.0-150400.9.3.1 |
| `python-aliyun-python-sdk-appmallsservice` | SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | All versions | 1.1.1-150400.10.3.1 |
| `python-aliyun-python-sdk-appstream-center` | SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | All versions | 1.0.1-150400.9.3.1 |
| `python-aliyun-python-sdk-aps` | SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | All versions | 1.0.0-150400.9.3.1 |
| `python-aliyun-python-sdk-arms` | SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | All versions | 2.7.30-150400.10.3.1 |
| `python-aliyun-python-sdk-arms4finance` | SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | All versions | 2.0.2-150400.10.3.1 |

Products: Pycryptodome Pycryptodome, Pycryptodome Pycryptodomex.

## How do I fix CVE-2023-52323?

Upgrade pycryptodome to 3.19.1 or later.

## Is CVE-2023-52323 being exploited?

There is no known exploitation of CVE-2023-52323 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2018-15560](https://insights.sbomify.com/CVE-2018-15560/): PyCryptodome integer overflow vulnerability (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-52323 and fix it if it is affected.

What it is: CVE-2023-52323 is a medium-severity vulnerability in n/a, published on 5 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-52323 in the wild and no public exploit code.

Affected packages and fixed versions:
- pycryptodome (PyPI): affected all versions; fixed in 3.19.1
- pycryptodome (PyPI): affected all versions; fixed in 3.19.1
- pycryptodome (PyPI): affected all versions; fixed in 3.19.1
- pycryptodomex (PyPI): affected all versions; fixed in 3.19.1
- pycryptodomex (PyPI): affected all versions; fixed in 3.19.1
- pycryptodomex (PyPI): affected all versions; fixed in 3.19.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-52323/ (Markdown: https://insights.sbomify.com/CVE-2023-52323/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-52323
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-52323
- OSV: https://osv.dev/vulnerability/CVE-2023-52323

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-52323/
Summaries are generated and may contain mistakes; the official description above is the record.
