M2crypto vulnerabilitiesRanked by how likely they are to be used.
M2crypto is made by M2crypto Project. We track 2 published vulnerabilities in it, across 41 versions. None of them is on the list of flaws known to be exploited today. If you run M2crypto, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which M2crypto vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of M2crypto's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which M2crypto flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 1.8%CVE-2020-25657Medium
A flaw was found in all released versions of m2crypto, where they are vulnerable to Bleichenbacher timing attacks in the RSA decryption API via the timed processing of valid PKCS#1 v1.5 Ciphertext.
- 1.1%CVE-2023-50781High
A flaw was found in m2crypto. This issue may allow a remote attacker to decrypt captured messages in TLS servers that use RSA key exchanges, which may lead to exposure of confidential or sensitive data.
Running M2crypto? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
A flaw was found in all released versions of m2crypto, where they are vulnerable to Bleichenbacher timing attacks in the RSA decryption API via the timed processing of valid PKCS#1 v1.5 Ciphertext. The highest threat from this vulnerability is to confidentiality.
- Matched to
- M2crypto on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 2 published vulnerabilities listed under the name M2crypto, across 41 versions.
None of M2crypto's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track M2crypto. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.