CVE-2024-4846
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 · uneditedAuthentication bypass in the 2FA feature in Devolutions Server 2024.1.14.0 and earlier allows an authenticated attacker to authenticate to another user without being asked for the 2FA via another browser tab.
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 confidenceAuthentication bypass in the 2FA feature allows an authenticated attacker to bypass 2FA requirements when authenticating to another user by leveraging another browser tab. The vulnerability appears to stem from improper session or state management where the 2FA challenge is not consistently enforced across concurrent sessions.
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< 2024.1.15.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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/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.
-
Identify Devolutions Server versionCheck the installed version of Devolutions Server. This is typically available in the Server Manager console under 'About' or in the installation directory readme/release notes. On the server, you can also check the installed programs list or the Devolutions Server management interface.Affected if The version is lower than 2024.1.15.0
-
Verify if 2FA is enabledIn Devolutions Server management console, navigate to User Management or Authentication settings to check if Two-Factor Authentication (2FA) is configured and enforced for users.Affected if 2FA is enabled and enforced in the environment
-
Review authentication logs for concurrent session anomaliesExamine Devolutions Server authentication logs for entries showing multiple concurrent authentication attempts or sessions for different users from the same source IP or browser within tight time windows, which could indicate exploitation attempts.Affected if Logs show suspicious concurrent session patterns that suggest 2FA bypass attempts
The environment is affected if Devolutions Server version is below 2024.1.15.0 AND 2FA is enabled, as this is the only scenario where the 2FA bypass vulnerability can be exploited.
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 · scoped2024.1.15.0
Upgrade Devolutions Server to a version newer than 2024.1.14.0. Until then, monitor authentication logs for suspicious concurrent session activity and consider implementing additional session coordination controls.
2024.1.15.0
- 1. Backup your current Devolutions Server database and configuration.
- 2. Verify current installed version by checking About or system information in Devolutions Server.
- 3. Download Devolutions Server version 2024.1.15.0 or later from the official Devolutions download page.
- 4. Apply the update following standard Devolutions Server upgrade procedures.
- 5. Verify the update was successful and the 2FA authentication flow now properly enforces 2FA across browser tabs.
- 6. Test that 2FA authentication works correctly for all users after the upgrade.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-4846 — 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-2024-4846 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