CVE-2020-25248
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 through 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. Directory traversal exists for reading files, as demonstrated by the FileName parameter.
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 confidenceDirectory traversal vulnerability in Hyland OnBase allows unauthenticated remote attackers to read arbitrary files on the server by manipulating the FileName parameter with path traversal sequences (e.g., ../../). This affects multiple version branches up to the listed thresholds.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 installed versionLocate the OnBase version information in the application (typically in Help > About, or check the installer logs, or query the registry on Windows servers under HKLM\SOFTWARE\Hyland\OnBase)Affected if The installed version falls within any of these ranges: <= 16.0.2.83; >= 17.0.0.0 and <= 17.0.2.109; >= 18.0.0.0 and <= 18.0.0.37; >= 19.0.0.0 and <= 19.8.16.1000; >= 20.0.0.0 and <= 20.3.10.1000
-
Confirm web access to OnBase is exposedVerify that the OnBase web client or API endpoints are accessible over HTTP/HTTPS from the network. The vulnerable parameter (FileName) is processed through the web interfaceAffected if The OnBase web interface is accessible externally or to untrusted users without authentication
-
Check for input validation on FileName parameterInspect any web application firewall (WAF), reverse proxy, or application-level input validation configurations that may inspect or block path traversal sequences (../, ..\) in request parametersAffected if No input validation or WAF rules are in place to filter or block path traversal characters in the FileName parameter
-
Review file system permissions on the application serverExamine the file system permissions on the OnBase application directory and critical system directories to determine if the application service account has unnecessary read access to sensitive files outside the intended web rootAffected if The OnBase service account has overly broad file system read permissions, allowing arbitrary file reads if the traversal vulnerability is exploited
You are affected if your installed OnBase version is within the vulnerable ranges AND the web interface is accessible, as the flaw allows unauthenticated path traversal via the FileName parameter to read arbitrary files.
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-provided patches for the specific OnBase version (patches above 16.0.2.83, 17.0.2.109, 18.0.0.37, 19.8.16.1000, and 20.3.10.1000). Additionally, implement strict input validation on the FileName parameter to reject path traversal characters and enforce least-privilege file system permissions on the application server.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25248 — 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-25248 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