Summary
Failing DTLS handshakes may cause throttling to block processing of records
Workarounds
none.
Impact
Failing handshakes didn't cleanup counters for throttling. In consequence the threshold may get reached and will not be released again. The results in permanently dropping records. The issues was reported for certificate based handshakes, but it can't be excluded, that this happens also for PSK based handshakes. It generally affects client and server as well.
CVE-2022-39368 has a CVSS score of 8.2 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.7.0, 2.7.4); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
main: commit 726bac57659410da463dcf404b3e79a7312ac0b9
2.7.x: commit 5648a0c27c2c2667c98419254557a14bac2b1f3f
Users are requested to update to 3.7.0. If Californium 2 support is required, users are requested to update to 2.7.4.
Frequently Asked Questions
- What is CVE-2022-39368? CVE-2022-39368 is a high-severity security vulnerability in org.eclipse.californium:scandium (maven), affecting versions >= 3.0.0, < 3.7.0. It is fixed in 3.7.0, 2.7.4.
- How severe is CVE-2022-39368? CVE-2022-39368 has a CVSS score of 8.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of org.eclipse.californium:scandium are affected by CVE-2022-39368? org.eclipse.californium:scandium (maven) versions >= 3.0.0, < 3.7.0 is affected.
- Is there a fix for CVE-2022-39368? Yes. CVE-2022-39368 is fixed in 3.7.0, 2.7.4. Upgrade to this version or later.
- Is CVE-2022-39368 exploitable, and should I be worried? Whether CVE-2022-39368 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2022-39368 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2022-39368?
- Upgrade
org.eclipse.californium:scandiumto 3.7.0 or later - Upgrade
org.eclipse.californium:scandiumto 2.7.4 or later
- Upgrade