CVE-2025-0217
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 · uneditedBeyondTrust Privileged Remote Access (PRA) versions prior to 25.1 are vulnerable to a local authentication bypass. A local authenticated attacker can view the connection details of a ShellJump session that was initiated with external tools, allowing unauthorized access to connected sessions.
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 confidenceBeyondTrust PRA versions prior to 25.1 have a local authentication bypass where a locally authenticated attacker can view connection details of ShellJump sessions initiated with external tools. This exposure of session connection information allows unauthorized access to connected 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< 25.1CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Verify BeyondTrust Privileged Remote Access is installedCheck for the presence of BeyondTrust PRA installation. Common locations include: Windows - C:\Program Files\BeyondTrust\Privileged Access or Linux - /opt/beyondtrust/pra. Use commands like 'ls' or check Programs and Features in Windows.Affected if BeyondTrust PRA software is present on the system
-
Determine installed version of BeyondTrust PRACheck the installed version. On Windows, examine the version information in Add/Remove Programs, or check version files in the installation directory. On Linux, run 'rpm -q' or 'dpkg -l' for the pra package, or inspect version files in the installation directory.Affected if The installed version is lower than 25.1 (e.g., 24.x, 23.x, etc.)
-
Identify if ShellJump sessions are configured with external toolsReview the BeyondTrust PRA configuration for ShellJump connections. Check the administrative console or configuration files for sessions defined as ShellJump that use external tools or jump points. Look for connection policies or session templates that specify external tool integration.Affected if ShellJump sessions configured to use external tools are present in the PRA configuration
You are affected if BeyondTrust Privileged Remote Access is installed with a version prior to 25.1 AND ShellJump sessions using external tools are configured on the system.
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 · scoped25.1
Upgrade BeyondTrust Privileged Remote Access to version 25.1 or later to remediate this vulnerability.
25.1
- Upgrade BeyondTrust Privileged Remote Access (PRA) to version 25.1 or later
- Follow standard BeyondTrust upgrade procedures for PRA, ensuring to back up configuration before upgrading
- After upgrade, verify the ShellJump session handling works correctly with external tools
- Confirm the authentication bypass vulnerability is resolved by testing that local authenticated users cannot view connection details of ShellJump sessions initiated with external tools
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0217 — 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-0217 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