dbcve.org
Privileged Remote AccessApplication · Beyondtrust

CVE-2023-4310

CRITICAL · 9.8 CVSS v3.1 Published 2023-09-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
BeyondTrust Privileged Remote Access (PRA) and Remote Support (RS) versions 23.2.1 and 23.2.2 contain a command injection vulnerability which can be exploited through a malicious HTTP request. Successful exploitation of this vulnerability can allow an unauthenticated remote attacker to execute underlying operating system commands within the context of the site user. This issue is fixed in version 23.2.3.

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

BeyondTrust PRA and RS versions 23.2.1 and 23.2.2 contain a command injection vulnerability that can be exploited through malicious HTTP requests. An unauthenticated remote attacker can execute operating system commands within the context of the site user, achieving critical impact (CVSS 9.8).

MitigationImmediately upgrade BeyondTrust PRA and RS to version 23.2.3 to remediate this vulnerability. Given the unauthenticated attack vector and critical severity, this upgrade should be prioritized as urgent.

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
Privileged Remote AccessApplication
Affected:= 23.2.1= 23.2.2
Remote SupportApplication
Affected:= 23.2.1= 23.2.2

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

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

  1. Identify the installed BeyondTrust product and version
    Access the product's web interface or admin console and locate the version information, typically found in the Help > About section or System Information page
    Affected if The version shown is exactly 23.2.1 or 23.2.2 for either Privileged Remote Access (PRA) or Remote Support (RS)
  2. Confirm product type is vulnerable
    Verify whether BeyondTrust Privileged Remote Access or BeyondTrust Remote Support is installed, as both products with the affected versions are vulnerable
    Affected if Either PRA or RS version 23.2.1 or 23.2.2 is installed
  3. Check if HTTP web interface is accessible
    Attempt to reach the BeyondTrust web portal via HTTP/HTTPS from a remote location or verify the service is running and listening on the expected ports
    Affected if The web interface is exposed and reachable, as the vulnerability is exploited through malicious HTTP requests

A system is affected if BeyondTrust PRA or RS version 23.2.1 or 23.2.2 is installed and the web interface is accessible, allowing unauthenticated remote command injection.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately upgrade BeyondTrust PRA and RS to version 23.2.3 to remediate this vulnerability. Given the unauthenticated attack vector and critical severity, this upgrade should be prioritized as urgent.

Recommended fix High confidence

23.2.3

  1. 1. Schedule a maintenance window for the BeyondTrust Privileged Remote Access (PRA) and/or Remote Support (RS) upgrade
  2. 2. Download BeyondTrust version 23.2.3 from the official BeyondTrust download portal or your licensed distribution channel
  3. 3. Review BeyondTrust upgrade documentation for your specific deployment type (appliance or software)
  4. 4. Perform a full backup of the current configuration before proceeding with the upgrade
  5. 5. Apply the upgrade to your PRA and/or RS installation following BeyondTrust's documented upgrade procedures
  6. 6. After upgrade completion, verify the system is operational and confirm the version number shows 23.2.3
  7. 7. Test that the web interface and remote access functionality are working correctly
Caveat Review BeyondTrust release notes for any configuration or behavioral changes between 23.2.x and 23.2.3; some custom settings may require adjustment

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

Fix this in Privileged Remote Access Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-4310 — 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-2023-4310 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