pycryptodome records
2 published records for vendor pycryptodome.
Researcher profile
- Entered KEV
- 0 · 0%
- Weaponized
- 0 · 0%
- Pre-auth RCE
- 0
- With a fix record
- 100%
- Median publish → KEV
- No record has entered KEV
Pre-auth RCE: flaws that let an attacker run code over the network without an account. Median publish → KEV: the typical time between a record being published and CISA listing it as exploited.
Attack profile
All records
2 records| Action | CVE | Vulnerability | Severity | EPSS · Published |
|---|---|---|---|---|
31Monitor | CVE-2018-15560No exploit | PyCryptodome before 3.6.6 has an integer overflow in the data_len variable in AESNI.c, related to the AESNI_encrypt and AESNI_decrypt functipycryptodome · pycryptodome · CWE-190 | High7.5 | 1.7%Aug 19, 2018 |
23Monitor | CVE-2023-52323No exploit | PyCryptodome and pycryptodomex before 3.19.1 allow side-channel leakage for OAEP decryption, exploitable for a Manger attack.pycryptodome · pycryptodome · CWE-203 | Medium5.9 | 0.6%Jan 5, 2024 |
- CVE-2018-1556031Monitor
PyCryptodome before 3.6.6 has an integer overflow in the data_len variable in AESNI.c, related to the AESNI_encrypt and AESNI_decrypt functi
HighCVSS 7.5No exploitEPSS 1%pycryptodome · pycryptodomeAug 19, 2018
- CVE-2023-5232323Monitor
PyCryptodome and pycryptodomex before 3.19.1 allow side-channel leakage for OAEP decryption, exploitable for a Manger attack.
MediumCVSS 5.9No exploitEPSS 0%pycryptodome · pycryptodomeJan 5, 2024