Californium vulnerabilitiesRanked by how likely they are to be used.
Californium is made by Eclipse. We track 4 published vulnerabilities in it, across 40 versions. None of them is on the list of flaws known to be exploited today. If you run Californium, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Californium vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Californium's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Californium 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.
- 0.9%CVE-2020-27222High
In Eclipse Californium version 2.3.0 to 2.6.0, the certificate based (x509 and RPK) DTLS handshakes accidentally fails, because the DTLS server side sticks to a wrong internal state.
- 0.6%CVE-2022-39368High
Eclipse Californium is a Java implementation of RFC7252 - Constrained Application Protocol for IoT Cloud services.
- 0.6%CVE-2022-2576High
In Eclipse Californium version 2.0.0 to 2.7.2 and 3.0.0-3.5.0 a DTLS resumption handshake falls back to a DTLS full handshake on a parameter mismatch without using a HelloVerifyRequest.
- 0.3%CVE-2021-34433High
In Eclipse Californium version 2.0.0 to 2.6.4 and 3.0.0-M1 to 3.0.0-M3, the certificate based (x509 and RPK) DTLS handshakes accidentally succeeds without verifying the server side's signature on the client side, if...
Running Californium? 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
In Eclipse Californium version 2.3.0 to 2.6.0, the certificate based (x509 and RPK) DTLS handshakes accidentally fails, because the DTLS server side sticks to a wrong internal state. That wrong internal state is set by a previous certificate based DTLS handshake failure with TLS parameter mismatch. The DTLS server side must be restarted to recover this. This allow clients to force a DoS.
- Matched to
- Californium 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 4 published vulnerabilities listed under the name Californium, across 40 versions.
None of Californium's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Californium. 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.