CVE-2025-34153
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 · uneditedHyland OnBase versions prior to 17.0.2.87 (other versions may be affected) are vulnerable to unauthenticated remote code execution via insecure deserialization on the .NET Remoting TCP channel. The service registers a listener on port 6031 with the URI endpoint TimerServer, implemented in Hyland.Core.Timers.dll. This endpoint deserializes untrusted input using the .NET BinaryFormatter, allowing attackers to execute arbitrary code under the context of NT AUTHORITY\SYSTEM.
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 prior to 17.0.2.87 contain an unauthenticated remote code execution vulnerability. The TimerServer endpoint on port 6031 deserializes untrusted input using the insecure .NET BinaryFormatter, allowing attackers to execute arbitrary code with NT AUTHORITY\SYSTEM privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 is installedLook for OnBase installation directories (commonly under C:\Program Files\Hyland or C:\Hyland) or check Windows Programs and Features for Hyland OnBase entriesAffected if OnBase is present on the system
-
Identify installed OnBase versionCheck the OnBase version information through the product itself, configuration files in the installation directory, or the Windows registry under HKLM\SOFTWARE\Hyland\OnBase if accessibleAffected if The installed version is lower than 17.0.2.87 (e.g., 17.0.2.x where x < 87, or any 17.0.x version below 17.0.2, or version 16.x or earlier)
-
Verify TimerServer is running and listeningRun netstat -an | findstr 6031 or use PowerShell Get-NetTCPConnection -LocalPort 6031 to check if port 6031 is in LISTEN stateAffected if Port 6031 is open and accepting connections (TimerServer is active)
-
Check if TimerServer is network-accessibleFrom an external perspective, attempt to telnet or connect to the target host on port 6031, or review firewall rules allowing inbound traffic to port 6031Affected if Port 6031 is exposed to untrusted networks or the internet
You are affected if Hyland OnBase version is below 17.0.2.87 AND the TimerServer service is running and accessible on port 6031, allowing unauthenticated attackers to send malicious binary-formatted payloads.
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 · scopedUpgrade to Hyland OnBase version 17.0.2.87 or later. As an immediate workaround, restrict network access to port 6031 or disable the TimerServer service until the patch can be applied.
17.0.2.87 or later
- Identify the current Hyland OnBase version by checking the application server or using the admin console
- Schedule a maintenance window for the upgrade process
- Perform a full backup of the OnBase application server and database before proceeding
- Download Hyland OnBase version 17.0.2.87 or later from the official Hyland support portal
- Follow Hyland's official upgrade documentation to apply the update
- After upgrade, verify that the TimerServer endpoint on port 6031 no longer accepts insecure deserialized data
- Confirm the upgrade was successful by checking the application version and functionality
- Monitor logs and system activity for any anomalies
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-34153 — 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-2025-34153 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