CVE-2020-25256
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 · uneditedAn issue was discovered in Hyland OnBase 16.0.2.83 and below, 17.0.2.109 and below, 18.0.0.37 and below, 19.8.16.1000 and below and 20.3.10.1000 and below. PKI certificates have a private key that is the same across different customers' installations.
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 confidenceHyland OnBase versions 16.0.2.83 and below, 17.0.2.109 and below, 18.0.0.37 and below, 19.8.16.1000 and below, and 20.3.10.1000 and below ship with PKI certificates containing the same private key across all customer installations. This cryptographic key reuse violates fundamental key isolation principles, allowing a compromised key from one customer to potentially compromise all other customers using the identical key.
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<= 16.0.2.83>= 17.0.0.0, <= 17.0.2.109>= 18.0.0.0, <= 18.0.0.37>= 19.0.0.0, <= 19.8.16.1000>= 20.0.0.0, <= 20.3.10.1000CVSS 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
- None
CVSS:3.1/AV:N/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Hyland OnBase installation versionLocate the OnBase installation directory and check the version information file, or use the OnBase configuration utility to display the installed version number.Affected if The installed version falls within any of these ranges: 16.0.2.83 or lower; 17.0.0.0 to 17.0.2.109; 18.0.0.0 to 18.0.0.37; 19.0.0.0 to 19.8.16.1000; or 20.0.0.0 to 20.3.10.1000
-
Locate installed PKI certificate filesNavigate to the OnBase certificate storage location (typically in the configuration or security folder within the OnBase installation directory) and identify the PKI certificate files used for authentication or encryption.Affected if PKI certificate files are present in the default OnBase certificate storage location.
-
Examine certificate private keyOpen or inspect the certificate file using a certificate viewing tool to examine the certificate details, particularly the public key fingerprint, issuer, and subject information. Compare the certificate thumbprint against the expected values for default OnBase certificates.Affected if The certificate displays characteristics consistent with the default PKI certificate shipped with OnBase (same issuer, same subject, same thumbprint as other OnBase installations of the same version).
You are affected if your OnBase version is within the affected ranges AND your installation is using the default PKI certificate that ships with the product, meaning your private key is identical to other OnBase installations.
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.
From vendor dataUpgrade to a version above the affected thresholds and regenerate unique PKI certificates for all installations, ensuring each customer has a distinct private key. Conduct a thorough audit of certificate integrity across the environment.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25256 — 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-2020-25256 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