dbcve.org
EjbcaApplication · Primekey

CVE-2020-11630

CRITICAL · 9.8 CVSS v3.1 Published 2020-04-08
Fix available
A fix is available. Upgrade to 6.15.2.6 / 7.3.1.2 or later.
See remediation →
100/100
Remediation priority · Urgent
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
An issue was discovered in EJBCA before 6.15.2.6 and 7.x before 7.3.1.2. In several sections of code, the verification of serialized objects sent between nodes (connected via the Peers protocol) allows insecure objects to be deserialized.

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

EJBCA before versions 6.15.2.6 and 7.x before 7.3.1.2 contains an insecure deserialization vulnerability in the Peers protocol that verifies serialized objects between connected nodes. The affected code sections allow insecure objects to be deserialized without proper validation, enabling remote code execution through malicious serialized payloads.

MitigationUpgrade EJBCA to version 6.15.2.6 or 7.3.1.2 or later. If immediate patching is not possible, restrict Peers protocol network access to trusted nodes only.

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
EjbcaApplication
Affected:< 6.15.2.6>= 7.0.0, < 7.3.1.2

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 EJBCA installation and version
    Locate the EJBCA installation directory and check the version file. Common locations include $EJBCA_HOME/dist/*.jar or check the admin web interface under 'About' or 'System Configuration'. Look for a version manifest or check the war file name.
    Affected if The installed version is less than 6.15.2.6, or is 7.0.0 through 7.3.1.1 (versions prior to 7.3.1.2)
  2. Verify Peers protocol is enabled
    Check the EJBCA configuration for Peers connector settings. In the admin web UI, navigate to 'System Configuration' > 'Peers' or check the peers.xml configuration file in the EJBCA conf directory.
    Affected if The Peers protocol feature is configured and active, enabling communication between EJBCA nodes
  3. Confirm Peers connector network binding
    Inspect the Peers connector configuration to determine which network interface and port it binds to. Check the server.xml or peer's configuration for the listener address.
    Affected if The Peers service listens on a non-loopback interface or is accessible from network segments containing untrusted nodes
  4. Review Peers trust relationships
    Examine the list of configured peer nodes in the Peers settings. Verify whether all peer connections are to trusted internal nodes only.
    Affected if Any peer connections exist to nodes that are not explicitly trusted or are external to the organization
  5. Check for deserialization gadget exposure
    Review system logs (usually in $EJBCA_HOME/logs/ or application logs) for any deserialization errors, unusual class loading messages, or unexpected serialized object traffic on the Peers port.
    Affected if Logs show deserialization exceptions or unexpected serialized traffic patterns

You are affected if EJBCA versions 6.x before 6.15.2.6 or 7.x before 7.3.1.2 are installed AND the Peers protocol feature is enabled and accessible to untrusted nodes.

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
Upgrade available Upgrade to 6.15.2.6 / 7.3.1.2 or later
Fixed in 6.15.2.67.3.1.2
Interim mitigation

Upgrade EJBCA to version 6.15.2.6 or 7.3.1.2 or later. If immediate patching is not possible, restrict Peers protocol network access to trusted nodes only.

Recommended fix High confidence

6.15.2.6 for 6.x branch or 7.3.1.2 for 7.x branch

  1. Identify the currently installed EJBCA version by checking the system or configuration files
  2. Determine whether you are on the 6.x or 7.x major version line
  3. For systems on 6.x versions: Plan upgrade to version 6.15.2.6 or later
  4. For systems on 7.x versions: Plan upgrade to version 7.3.1.2 or later
  5. Review EJBCA upgrade documentation for your deployment type (ejbca upgrade guide)
  6. Create a full backup of the database and configuration files before upgrading
  7. Stop EJBCA services
  8. Perform the upgrade following vendor-specific procedures for your deployment
Caveat Review release notes for your specific version jump to check for database schema changes, API changes, or configuration format updates that may require adjustment

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

Fix this in Ejbca Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-11630 — 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-2020-11630 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