dbcve.org
Devolutions ServerApplication · Devolutions

CVE-2025-2277

HIGH · 7.5 CVSS v3.1 Published 2025-03-13
Fix available
A fix is available. Upgrade to 2025.1.3.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Exposure of password in web-based SSH authentication component in Devolutions Server 2024.3.13 and earlier allows a user to unadvertently leak his SSH password due to missing password masking.

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 confidence

Devolutions Server's web-based SSH authentication component fails to mask password input characters, causing SSH credentials to be displayed in plain text on the login form. This allows unintended observers to view the password during entry, leading to credential exposure through shoulder surfing, screen sharing, or recorded sessions.

MitigationImplement proper password masking (e.g., using password input type or a masking library) in the SSH authentication web form, and upgrade to a version after 2024.3.13 once the vendor releases a patched version.

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
Devolutions ServerApplication
Affected:< 2025.1.3.0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Devolutions Server version
    Identify the installed version of Devolutions Server. This can be found in Windows Programs and Features, the server's web interface About/Help section, or the installation directory's version file. Compare your version number to the affected range.
    Affected if The installed version is earlier than 2025.1.3.0
  2. Verify web SSH login is accessible
    Access the Devolutions Server web interface and navigate to the SSH authentication or remote session login page. Confirm that the web-based SSH login form is available and being used.
    Affected if The web-based SSH authentication form is accessible and in use
  3. Inspect password field masking
    Open the Devolutions Server SSH login page in a web browser. Use browser developer tools (F12) to inspect the HTML input element for the password field. Check whether the input type attribute is set to 'password' (which masks characters) or 'text' (which displays them in plain text).
    Affected if The password input field uses type='text' or lacks proper password masking

A user is affected if they run Devolutions Server version earlier than 2025.1.3.0 and use the web-based SSH authentication interface where password characters are visible instead of masked.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2025.1.3.0 or later
Fixed in 2025.1.3.0
Interim mitigation

Implement proper password masking (e.g., using password input type or a masking library) in the SSH authentication web form, and upgrade to a version after 2024.3.13 once the vendor releases a patched version.

Recommended fix High confidence

2025.1.3.0

  1. 1. Verify current Devolutions Server version by accessing the administration console or checking the About section
  2. 2. Create a complete backup of the Devolutions Server database and configuration files
  3. 3. Download the latest Devolutions Server installer (version 2025.1.3.0 or later) from the official Devolutions download portal
  4. 4. Stop the Devolutions Server service before applying the update
  5. 5. Run the installer and follow the on-screen prompts to upgrade to version 2025.1.3.0
  6. 6. After installation completes, restart the Devolutions Server service
  7. 7. Verify the upgrade was successful by checking the version number in the administration console
  8. 8. Test the web-based SSH authentication component to confirm password masking is now working correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Devolutions Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-2277 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-2277 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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