CVE-2024-11671
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 authentication in SQL data source MFA validation in Devolutions Remote Desktop Manager 2024.3.17 and earlier on Windows allows an authenticated user to bypass the MFA validation via data source switching.
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 confidenceThis is an authentication bypass vulnerability in Devolutions Remote Desktop Manager where an authenticated user can bypass Multi-Factor Authentication (MFA) validation for SQL data sources by switching between data sources. The improper authentication logic in the MFA validation allows a local authenticated attacker to circumvent the second factor security control.
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.3.18.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
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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.
-
Check installed version of Remote Desktop ManagerOpen the application, then navigate to Help > About or check the installed version via the Windows Programs and Features list. Compare the version number to the affected range: any version before 2024.3.18.0 is vulnerable.Affected if The installed version is earlier than 2024.3.18.0
-
Verify SQL data source configurationOpen Remote Desktop Manager and check the data sources configured in the application. Look for SQL-based data sources such as Microsoft SQL Server, MySQL, PostgreSQL, or other SQL database connections listed in the data source panel.Affected if SQL data sources are configured and in use
-
Confirm MFA is enabled on SQL data sourcesIn Remote Desktop Manager, select each SQL data source and inspect its properties or security settings. Check if Multi-Factor Authentication is configured or enabled for the data source connection.Affected if MFA is enabled on any SQL data source and the application version is vulnerable
-
Review connection logs for data source switching activityAccess the application logs or Windows event logs related to Remote Desktop Manager. Search for rapid or repeated switching between different data sources, especially SQL data sources, which may indicate exploitation attempts.Affected if Logs show unusual data source switching patterns by authenticated users
A user is affected if they are running any version of Remote Desktop Manager before 2024.3.18.0 with SQL data sources that have MFA enabled.
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.3.18.0
Upgrade Devolutions Remote Desktop Manager to a version newer than 2024.3.17 where the MFA bypass vulnerability is patched. Review access logs for suspicious data source switching activity indicative of exploitation.
2024.3.18.0
- 1. Check current Remote Desktop Manager version by opening the application and navigating to Help > About or using the version indicator in the title bar
- 2. Download Remote Desktop Manager version 2024.3.18.0 or later from the official Devolutions website (https://devolutions.net/remote-desktop-manager)
- 3. Close Remote Desktop Manager completely before upgrading
- 4. Run the installer and follow the on-screen prompts to upgrade the application
- 5. After installation, verify the version by checking Help > About to confirm version 2024.3.18.0 or later is installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-11671 — 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-11671 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