CVE-2024-12356
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 · uneditedA critical vulnerability has been discovered in Privileged Remote Access (PRA) and Remote Support (RS) products which can allow an unauthenticated attacker to inject commands that are run as a site user.
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 confidenceCommand injection vulnerability in BeyondTrust Privileged Remote Access (PRA) and Remote Support (RS) products allowing unauthenticated attackers to inject and execute arbitrary OS commands as a site user context.
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<= 24.3.1<= 24.3.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed BeyondTrust productCheck for presence of BeyondTrust Privileged Remote Access or Remote Support by reviewing installed software list, service names, or checking common installation paths such as C:\Program Files\BeyondTrust\ or /opt/beyondtrust/Affected if Either BeyondTrust PRA or RS is installed on the system
-
Determine installed versionLocate the version information in the product interface under Help > About, or check the installer/log files, or query the product's API endpoint if accessibleAffected if The installed version is 24.3.1 or lower for either product
-
Verify product interface is network accessibleCheck network configuration, firewall rules, or reverse proxy settings to determine if the PRA/RS web interface ports (default 443, 8443) are exposed to untrusted networksAffected if The management interface is reachable from networks other than trusted administration networks
-
Check for unauthorized user accounts or sessionsReview the BeyondTrust administrative console for unauthorized site users, unexpected sessions, or newly created accounts in the Users & Sessions dashboardAffected if Unknown users or sessions exist that were not created by legitimate administrators
-
Inspect system for signs of command executionReview system logs, application logs, and network traffic logs for suspicious commands, unexpected scripts, or connections to unknown external IPs around the time frame of the vulnerability disclosureAffected if Evidence of unexpected command execution or unauthorized access attempts are found in logs
You are affected if BeyondTrust PRA or RS version 24.3.1 or lower is installed and its management interface is network-accessible to untrusted users.
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 · scopedApply vendor-provided security patch immediately; prior to patch deployment, implement network segmentation and restrict access to PRA/RS management interfaces from untrusted networks.
Contact BeyondTrust for the specific fixed release (version > 24.3.1)
- 1. Identify all affected BeyondTrust Privileged Remote Access (PRA) and Remote Support (RS) installations in your environment.
- 2. Check the current version of each installation to confirm it is <= 24.3.1.
- 3. Contact BeyondTrust support or visit the official BeyondTrust security advisory page to obtain the specific patched version for your product.
- 4. Schedule a maintenance window for the upgrade following your organization's change management procedures.
- 5. Before upgrading, backup all configuration data and ensure you have a rollback plan.
- 6. Upgrade the affected installations to the fixed release (version > 24.3.1) as specified in the BeyondTrust security advisory.
- 7. After upgrading, verify the vulnerability is remediated by confirming the version number and optionally testing that unauthenticated command injection is no longer possible.
- 8. Document the remediation activities for audit purposes.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12356 — 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-12356 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