CVE-2025-3768
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 · uneditedImproper access control in Tor network blocking feature in Devolutions Server 2025.1.10.0 and earlier allows an authenticated user to bypass the tor blocking feature when the Devolutions hosted endpoint is not reachable.
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 confidenceImproper access control in Devolutions Server's Tor network blocking feature allows authenticated users to bypass Tor blocking when the hosted endpoint is unreachable. The vulnerability stems from conditional access control logic that fails to enforce Tor blocking during fallback or degraded connectivity scenarios.
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<= 2025.1.10.0CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L
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.
-
Determine your Devolutions Server versionLocate and inspect the installed version of Devolutions Server in your environment (typically accessible via the product interface, about section, or installed programs list)Affected if The installed version is 2025.1.10.0 or any earlier version
-
Verify if Tor blocking is configuredCheck the Devolutions Server security or network settings for any Tor network blocking configurationAffected if Tor blocking is explicitly enabled in the product configuration
-
Identify the hosted endpoint configurationLocate the settings that define the hosted endpoint URL or address that Devolutions Server connects toAffected if A hosted endpoint is configured and referenced in the product settings
-
Test network connectivity to the hosted endpointAttempt to reach the hosted endpoint from the Devolutions Server system using standard network diagnostic methodsAffected if The hosted endpoint becomes unreachable or experiences degraded connectivity while Tor blocking is enabled
-
Confirm fallback connectivity scenario existsObserve whether Devolutions Server enters a fallback, degraded, or alternative connectivity mode when the primary hosted endpoint is unavailableAffected if The system falls back to alternative connectivity paths while Tor blocking is meant to be enforced
You are affected if your Devolutions Server version is 2025.1.10.0 or earlier, Tor blocking is enabled, and the hosted endpoint becomes unreachable causing a fallback scenario where Tor traffic could bypass the blocking logic.
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 Devolutions Server version 2025.1.11.0 or later. Until then, monitor network connectivity to the hosted endpoint and implement additional network-level Tor filtering as a compensating control.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3768 — 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-3768 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