dbcve.org
JerseyApplication · Eclipse

CVE-2025-12383

HIGH · 7.4 CVSS v3.1 Published 2025-11-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In Eclipse Jersey versions 2.45, 3.0.16, 3.1.9 a race condition can cause ignoring of critical SSL configurations - such as mutual authentication, custom key/trust stores, and other security settings. This issue may result in SSLHandshakeException under normal circumstances, but under certain conditions, it could lead to unauthorized trust in insecure servers (see PoC)

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A race condition in Eclipse Jersey versions 2.45, 3.0.16, and 3.1.9 causes SSL configuration parameters (mutual authentication, custom key/trust stores, and other security settings) to be ignored during client/server initialization. This timing vulnerability can result in SSLHandshakeExceptions under normal conditions or allow unauthorized trust in insecure servers when the race condition favors insecure defaults.

MitigationUpgrade to patched versions of Eclipse Jersey beyond 2.45, 3.0.16, and 3.1.9. Alternatively, audit all SSL-dependent Jersey client/server configurations to verify they are not vulnerable to the race window.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JerseyApplication
Affected:= 2.45= 3.0.16= 3.1.9

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Eclipse Jersey version
    Locate the jersey-common, jersey-client, or jersey-server JAR files in your classpath or dependencies (check Maven pom.xml, Gradle build files, or application lib directory) and read the version from the JAR manifest or dependency declaration
    Affected if The installed version matches exactly 2.45, 3.0.16, or 3.1.9
  2. Determine if SSL configuration is used
    Search your codebase for JerseyClient, JerseyClientBuilder, ClientBuilder, or Server configuration classes that set SSL-related properties such as keyStore, trustStore, hostnameVerifier, or SSLContext
    Affected if Your application initializes Jersey clients or servers with custom SSL configuration (mutual authentication, custom key/trust stores, or specific SSLContext)
  3. Verify SSL initialization behavior
    Enable SSL debug logging (set javax.net.debug=ssl:handshake) and observe during client/server startup whether SSL handshake errors occur unexpectedly, or review logs for SSLHandshakeException messages that indicate SSL settings were ignored
    Affected if SSLHandshakeExceptions occur during initialization despite proper SSL configuration, or connections succeed when they should fail certificate validation

You are affected if you run exactly version 2.45, 3.0.16, or 3.1.9 of Eclipse Jersey AND use SSL configuration for Jersey client/server initialization, as the race condition may cause your SSL settings to be ignored.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to patched versions of Eclipse Jersey beyond 2.45, 3.0.16, and 3.1.9. Alternatively, audit all SSL-dependent Jersey client/server configurations to verify they are not vulnerable to the race window.

Recommended fix Moderate confidence

Jersey 2.46+ (2.x line), 3.0.17+ (3.0.x line), or 3.1.10+ (3.1.x line)

  1. 1. Identify the Jersey version currently in use by checking your project's dependency management (Maven pom.xml, Gradle build.gradle, or similar)
  2. 2. For Jersey 2.x users: Upgrade jersey-client and jersey-common dependencies from version 2.45 to version 2.46 or later
  3. 3. For Jersey 3.0.x users: Upgrade org.glassfish.jersey.* dependencies from version 3.0.16 to version 3.0.17 or later
  4. 4. For Jersey 3.1.x users: Upgrade org.glassfish.jersey.* dependencies from version 3.1.9 to version 3.1.10 or later
  5. 5. Rebuild and test your application to verify SSL configuration is applied correctly, especially mutual TLS authentication and custom key/trust stores
  6. 6. Verify no regressions in SSL/TLS functionality
Caveat Minor version upgrades typically maintain backward compatibility but always review release notes for security-related changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jersey Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12383 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-12383 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data