CVE-2022-42954
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 · uneditedKeyfactor EJBCA before 7.10.0 allows XSS.
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 confidenceKeyfactor EJBCA before version 7.10.0 contains a Cross-Site Scripting (XSS) vulnerability. The specific location and attack vector are not detailed in the available description, but XSS vulnerabilities in EJBCA typically involve unsanitized user input being rendered in web interfaces related to certificate management or administrative panels.
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< 7.10.0CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed EJBCA versionLocate the EJBCA installation directory and check the version file or startup logs. Common locations include the manifest file, about page in the admin web interface, or the version reported by the EJBCA service/command-line tools.Affected if The installed version is lower than 7.10.0 (for example, 7.9.x, 7.8.x, or earlier)
-
Confirm EJBCA web interface is activeVerify that the EJBCA admin or user web interface is deployed and accessible. Check if the application server (such as JBoss, WildFly, or Tomcat) is running and serving the EJBCA web applications.Affected if The web interface is publicly or internally accessible and the installed version is below 7.10.0
-
Review web interface configurationInspect the EJBCA web application configuration files (such as web.xml) and the application server configuration to confirm which web interfaces are enabled, particularly administrative panels and certificate management portals.Affected if Administrative or user-facing web interfaces are enabled and the installed version is below 7.10.0
You are affected if your EJBCA installation is version 7.9.x or earlier AND the EJBCA web interface (admin or user portal) is accessible, as the XSS vulnerability exists in these web components.
Generated from the published advisory. Verify against your own configuration.
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 · scoped7.10.0
Upgrade EJBCA to version 7.10.0 or later to obtain the vendor fix. Prior to upgrade, conduct thorough testing in a non-production environment given this is a PKI system.
Keyfactor EJBCA 7.10.0 or later
- 1. Back up the current EJBCA configuration and database before upgrading.
- 2. Download Keyfactor EJBCA version 7.10.0 or later from the official Keyfactor support portal.
- 3. Review the upgrade guide for migrating from your current version to 7.10.0.
- 4. Perform the upgrade in a staging or test environment first to validate functionality.
- 5. After successful testing, apply the upgrade to the production environment.
- 6. Verify the XSS vulnerability is resolved by testing the previously vulnerable endpoints.
- 7. Monitor for any post-upgrade issues and have a rollback plan ready.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-42954 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-42954 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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