dbcve.org
EjbcaApplication · Keyfactor

CVE-2023-34196

HIGH · 8.2 CVSS v3.1 Published 2023-08-03
Fix available
A fix is available. Upgrade to 8.0.0 or later.
See remediation →
91/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
In the Keyfactor EJBCA before 8.0.0, the RA web certificate distribution servlet /ejbca/ra/cert allows partial denial of service due to an authentication issue. In configurations using OAuth, disclosure of CA certificates (attributes and public keys) to unauthenticated or less privileged users may occur.

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 · moderate confidence

The Keyfactor EJBCA RA web certificate distribution servlet (/ejbca/ra/cert) contains an authentication bypass that enables partial denial of service. Additionally, in configurations using OAuth authentication, the vulnerability allows disclosure of CA certificate attributes and public keys to unauthenticated or less privileged users.

MitigationUpgrade to EJBCA version 8.0.0 or later. Organizations using OAuth configurations should prioritize this upgrade given the certificate disclosure risk to unauthorized users.

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:< 8.0.0

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
None
Availability
Low

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

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
    Check the EJBCA installation directory for version information. Common locations include: examine the pom.xml or version file in the EJBCA installation root, check the admin web interface version display, or run 'ejbca.sh version' or 'ejbca.bat version' if CLI tools are available.
    Affected if The installed version is any version prior to 8.0.0 (e.g., 7.x, 6.x series)
  2. Verify the RA servlet is accessible
    Attempt to access the endpoint /ejbca/ra/cert via HTTP/HTTPS request from an unauthenticated context. This can be done with curl or a browser: curl -k https://<server>/ejbca/ra/cert
    Affected if The endpoint responds with any server behavior (even an error page indicates the servlet is exposed rather than being blocked at the network or application layer)
  3. Check OAuth authentication configuration
    Inspect the EJBCA configuration files (typically in conf/ or config directory) for OAuth-related settings. Look for configuration keys containing 'oauth', 'OAuth', or authentication module definitions that reference OAuth providers in the server.xml or ejbca.properties files.
    Affected if OAuth authentication is enabled as the primary or secondary authentication mechanism for the RA interface
  4. Review access control configuration for RA endpoints
    Examine the access rules in EJBCA's authorization configuration, typically found in the admin web interface under Access Control or in the external XML access rules file. Verify whether /ejbca/ra/cert has proper authentication requirements enforced.
    Affected if The RA certificate endpoint lacks enforced authentication or permits anonymous/less-privileged access

A defender is affected if EJBCA version is below 8.0.0 and the /ejbca/ra/cert servlet is exposed without proper authentication controls, especially if OAuth authentication is in use.

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 8.0.0 or later
Fixed in 8.0.0
Interim mitigation

Upgrade to EJBCA version 8.0.0 or later. Organizations using OAuth configurations should prioritize this upgrade given the certificate disclosure risk to unauthorized users.

Recommended fix High confidence

EJBCA 8.0.0 or later

  1. 1. Back up your current EJBCA installation, database, and configuration files
  2. 2. Review the EJBCA 8.0.0 release notes and migration guide for any configuration or compatibility changes
  3. 3. Upgrade your EJBCA installation to version 8.0.0 or later
  4. 4. After upgrade, verify the /ejbca/ra/cert servlet now properly enforces authentication
  5. 5. If using OAuth configuration, verify CA certificates are no longer exposed to unauthenticated users
  6. 6. Test certificate enrollment workflows to ensure normal operation
Caveat Review EJBCA 8.0.0 release notes for any breaking changes specific to your configuration

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

Fix this in Ejbca 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 the upgrade done

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-2023-34196 — 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-2023-34196 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