CVE-2020-27222

7.5 HIGH

📋 TL;DR

This vulnerability in Eclipse Californium allows clients to cause a denial-of-service (DoS) by exploiting a DTLS handshake state error. The DTLS server enters a wrong internal state after a failed certificate-based handshake, requiring a server restart to recover. This affects systems using Eclipse Californium versions 2.3.0 through 2.6.0 with DTLS enabled.

💻 Affected Systems

Products:
  • Eclipse Californium
Versions: 2.3.0 to 2.6.0
Operating Systems: All operating systems running affected Californium versions
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects systems using DTLS with certificate-based authentication (x509 or RPK). Plain CoAP without DTLS is not affected.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete unavailability of DTLS services requiring manual server restarts, potentially disrupting IoT or CoAP communications.

🟠

Likely Case

Intermittent DoS affecting DTLS connections, requiring administrative intervention to restart services.

🟢

If Mitigated

Minimal impact with proper network segmentation and monitoring to detect and respond to attack attempts.

🌐 Internet-Facing: HIGH - Internet-facing DTLS servers are directly exposed to attack from any client.
🏢 Internal Only: MEDIUM - Internal attackers or compromised internal systems could still exploit this vulnerability.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Exploitation requires sending DTLS handshake requests but no special tools or authentication needed.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 2.7.0

Vendor Advisory: https://bugs.eclipse.org/bugs/show_bug.cgi?id=570844

Restart Required: Yes

Instructions:

1. Upgrade to Eclipse Californium 2.7.0 or later. 2. Replace the affected Californium library in your application. 3. Restart all services using Californium.

🔧 Temporary Workarounds

Disable DTLS

all

Temporarily disable DTLS if certificate-based authentication is not required

Configure Californium to use plain CoAP without DTLS

Implement connection limiting

all

Limit DTLS handshake attempts from single IP addresses

Use firewall rules or application-level rate limiting

🧯 If You Can't Patch

  • Implement network segmentation to isolate DTLS servers from untrusted networks
  • Deploy monitoring to detect abnormal DTLS handshake patterns and trigger alerts

🔍 How to Verify

Check if Vulnerable:

Check if using Eclipse Californium version 2.3.0-2.6.0 with DTLS enabled for certificate-based authentication

Check Version:

Check application dependencies or Californium library version in build configuration

Verify Fix Applied:

Verify Californium version is 2.7.0 or later and test DTLS handshake functionality

📡 Detection & Monitoring

Log Indicators:

  • Multiple DTLS handshake failures from same source
  • DTLS server restart events
  • Certificate validation errors followed by service degradation

Network Indicators:

  • Abnormal DTLS handshake patterns
  • Increased DTLS traffic from single sources
  • DTLS connection timeouts

SIEM Query:

source="californium-logs" AND (message="DTLS handshake failure" OR message="certificate validation error") | stats count by src_ip

🔗 References

📤 Share & Export