CVE-2024-40595
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 · uneditedAn authentication-bypass issue in the RDP component of One Identity Safeguard for Privileged Sessions (SPS) On Premise before 7.5.1 (and LTS before 7.0.5.1) allows man-in-the-middle attackers to obtain access to privileged sessions on target resources by intercepting cleartext RDP protocol information.
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 confidenceAn authentication-bypass vulnerability in the RDP component of One Identity Safeguard for Privileged Sessions allows man-in-the-middle attackers to intercept cleartext RDP protocol traffic and obtain unauthorized access to privileged sessions on target resources.
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
- Adjacent
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if One Identity Safeguard for Privileged Sessions is installedCheck system inventory, installed software, or running services for One Identity SPS or Safeguard for Privileged SessionsAffected if The product is present on the system
-
Determine the installed SPS versionAccess the SPS admin interface or use the product's version command/query mechanism, then compare against the fixed versions 7.5.1 and LTS 7.0.5.1Affected if The installed version is lower than 7.5.1 or lower than LTS 7.0.5.1
-
Verify if RDP session recording or RDP proxy is enabledCheck SPS configuration for enabled RDP connection policies, session recording policies, or RDP proxy featuresAffected if RDP component is actively configured and processing RDP traffic
-
Check RDP encryption settingsInspect SPS RDP connection policy settings to determine if TLS encryption is enforced or if cleartext RDP traffic is permittedAffected if Cleartext RDP traffic is allowed or TLS encryption is not enforced on RDP connections
User is affected if One Identity SPS is running with RDP enabled and the version is below 7.5.1 (or below LTS 7.0.5.1) with unencrypted RDP traffic permitted.
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 One Identity SPS to version 7.5.1 or LTS 7.0.5.1 or later to remediate this vulnerability. Additionally, ensure network segmentation and TLS encryption are enforced to protect RDP traffic from interception.
SPS 7.5.1 (or LTS 7.0.5.1)
- 1. Log in to the One Identity Safeguard for Privileged Sessions (SPS) administrative interface.
- 2. Navigate to the version check or system update section.
- 3. Verify current SPS version is before 7.5.1 (or before 7.0.5.1 for LTS branch).
- 4. Schedule a maintenance window for the upgrade.
- 5. Download SPS version 7.5.1 or later (or LTS 7.0.5.1 or later) from the One Identity support portal.
- 6. Apply the upgrade following One Identity's standard upgrade procedure.
- 7. After upgrade, verify the RDP connections are using encrypted channel to prevent MITM attacks.
- 8. Test RDP sessions to confirm functionality and security.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-40595 — 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-40595 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