Skip to content

Security: eclipse-californium/californium

SECURITY.md

Security Policy

This Eclipse Foundation Project adheres to the Eclipse Foundation Vulnerability Reporting Policy.

How To Report a Vulnerability

If you think you have found a vulnerability in this repository, please report it to us through coordinated disclosure.

Please do not report security vulnerabilities through public issues, discussions, or change requests.

Instead, report it using one of the following ways:

  • Create a confidential issue in the Eclipse Foundation Vulnerability Reporting Tracker (requires Eclipse account)
  • Report a vulnerability directly via private vulnerability reporting on GitHub

You can find more information about reporting and disclosure at the Eclipse Foundation Security page.

Please include as much of the information listed below as you can to help us better understand and resolve the issue:

  • The type of issue (e.g., buffer overflow, SQL injection, or cross-site scripting)
  • Affected version(s)
  • Impact of the issue, including how an attacker might exploit the issue
  • Step-by-step instructions to reproduce the issue
  • The location of the affected source code (tag/branch/commit or direct URL)
  • Full paths of source file(s) related to the manifestation of the issue
  • Configuration required to reproduce the issue
  • Log files that are related to this issue (if possible)
  • Proof-of-concept or exploit code (if possible)

This information will help us triage your report more quickly.

Supported Versions

Version Supported
4.0.0-SNAPSHOT (main) ✔️
4.0.0-M6 ✔️
3.14.0 ✔️
3.13.0, 3.12.1, 3.11.0,
3.10.0, 3.9.1, 3.8.0,
3.7.0, 3.6.0, 3.5.0,
3.4.0,3.3.1, 3.2.0,
3.1.0, 3.0.0
2.8.0
2.7.4, 2.6.6, 2.5.0,
2.4.1, 2.3.1, 2.2.3,
2.1.0, 2.0.0
before 2.0.0

✔️ development version / current release - all bugfixes will be applied

❓ the previous (bugfix-)releases - update to the current release is recommended. On exceptions, specific bugfixes may be applied on request. (Create a vulnerability report with the requested vulnerability fix and the (bugfix-)version.)

❌ old releases, milestone releases - usually no bugfixes are applied there.

Known Vulnerabilities

Californium Version Vulnerability
< 3.7
< 2.7.4
Failing DTLS handshake CVE-2022-39368
< 3.6
< 2.7.3
DTLS resumption handshake CVE-2022-2576
< 3.0-M3
< 2.6.5
DTLS certificates verification bypass CVE-2021-34433
< 2.6.0 DTLS certificates verification fails sticky CVE-2020-27222

See also NIST database of known Californium vulnerabilities

Known Vulnerabilities Of Dependencies

Californium Version Dependency Affected Version Usage Vulnerability
4.0.0-M1 - 4.0.0-M3 org.apache.httpcomponents.client5 5.4 - 5.4.2 coap-http-cross-proxy CVE-2025-27820
< 3.6
< 2.7.3
com.google.code.gson < 2.8.9 demo-apps CVE 2022-25647
< 3.3
< 2.7.2
com.upokecenter.cbor 4.0 - 4.5.0 cf-oscore
demo-apps
GHSA-fj2w-wfgv-mwq6
< 3.2
< 2.7.1
ch.qos.logback.logback-classic < 1.2.9 demo-apps CVE-2021-42550

Known Vulnerabilities Of Runtime Dependencies

Californium Version Dependency Affected Version Usage Vulnerability
< 3.5 JDK / JCE <= 15.0.2?
<= 16.0.2?
< 17.0.3
< 18.0.1
execution environment ECDSA CVE-2022-21449
< 3.10 logback < 1.2.13 logging implementation Remote appender CVE-2023-6378
CVE-2023-6481
Learn more about advisories related to eclipse-californium/californium in the GitHub Advisory Database