CVE-2020-25255
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. It allows remote attackers to cause a denial of service (outage of connection-request processing) via a long user ID, which triggers an exception and a large log entry.
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 contains a denial-of-service vulnerability where a long user ID triggers an unhandled exception, resulting in a large log entry that disrupts connection-request processing. The issue stems from insufficient input validation on the user ID field, allowing remote attackers to send excessively long strings that cause the service to fail.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed OnBase versionLocate the OnBase version information in your installation - typically found in the product UI under Help > About, or in registry entries or configuration files depending on deployment method. Compare the version number against the affected ranges: <= 16.0.2.83; 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; 20.0.0.0 to 20.3.10.1000Affected if The installed version falls within any of the affected version ranges listed above
-
Confirm user authentication endpoint is exposedDetermine if the OnBase user authentication interface is accessible from the network. This typically involves the OnBase web server or application server components that handle login requests. Check network access controls and firewall rules for the OnBase authentication portsAffected if The OnBase authentication endpoint is externally accessible or accessible to untrusted networks
-
Inspect application logs for exception indicatorsExamine OnBase application logs for unhandled exceptions related to user ID processing. Look for patterns indicating unusually large log entries or stack traces occurring during authentication attempts. The vulnerability causes large log entries when excessively long user ID strings are submittedAffected if Logs contain large or excessive entries tied to user ID input fields, or unhandled exceptions during authentication processing
You are affected if your OnBase version is within the vulnerable ranges AND the authentication interface is accessible, as indicated by large log entries from long user ID strings causing service disruption.
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 dataApply the vendor-provided security patches for all affected OnBase versions (16.x, 17.x, 18.x, 19.8.x, and 20.3.x). Implement input length validation on user ID fields as a compensating control until patches can be applied.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25255 — 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-25255 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