CVE-2020-25250
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. Client applications can write arbitrary data to the server logs.
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 allows client applications to write arbitrary data to server logs without proper input validation. This log injection vulnerability enables attackers to inject false log entries or malicious content that could be interpreted when logs are viewed or processed by other systems.
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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Confirm Hyland OnBase installation existsCheck for OnBase installation directories (commonly C:\Program Files\Hyland\OnBase or C:\Hyland\OnBase) or look for the OnBase service running in Windows Services or Linux service listingsAffected if OnBase server software is installed
-
Identify installed OnBase versionCheck the OnBase version information: look for version.txt, About dialog in the OnBase client, or check the Windows Registry under HKLM\SOFTWARE\Hyland\OnBase\ProductVersion. In the installation directory, check bin/ProductVersion.info or similar version metadata files.Affected if A version number is found that matches the affected ranges below
-
Compare version to affected rangesCompare your installed version to these vulnerable ranges: 16.0.2.83 and 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; 20.0.0.0 to 20.3.10.1000Affected if Your installed version falls within any of these ranges (less than or equal to 16.0.2.83, 17.0.2.109, 18.0.0.37, 19.8.16.1000, or 20.3.10.1000)
-
Verify client application log write accessReview OnBase configuration for client-side logging settings. Check if client applications are permitted to submit log entries to the server, typically via the Diagnostics or Logging configuration panels in the OnBase Administration module.Affected if Client applications have the ability to write directly to server logs (this is the default behavior in affected versions)
You are affected if Hyland OnBase is installed and the installed version falls within any of the vulnerable version ranges (16.x through 20.3.10.1000), since the vulnerability exists in how the server handles log input from client applications.
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 vendor-supplied patches for affected versions (16.0.2.84+, 17.0.2.110+, 18.0.0.38+, 19.8.16.1001+, 20.3.10.1001+). Until patched, monitor logs for suspicious injection patterns and restrict client application access where possible.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25250 — 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-25250 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