Command Injection vulnerability in Remote Support (RS) & Privilege Remote Access (PRA) (CVE-2024-12686)
Published In CISA KEV since Sources: SingCERT, pwn.watch, CVE.org
- Actively exploited
- Source: CSA/SingCERT How we classify
What is affected, what to do
A vulnerability has been discovered in Privileged Remote Access (PRA) and Remote Support (RS) which can allow an attacker with existing administrative privileges to inject commands and run as a site user.
The vulnerability is being actively exploited; treat it as a priority. The available sources name no fixed version. Check the vendor guidance in the references below. Immediate actions, mitigation and detection rules are in the runbook below.
- Affected
- BeyondTrust Remote Support (RS) & Privileged Remote Access (PRA)
lte *..24.3.1
- BeyondTrust Remote Support (RS) & Privileged Remote Access (PRA)
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
7.2
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: NVD, CVSS v3
6.6
CVSS v3
Severity Medium on the scale from 0 to 10.
Source: SingCERT, pwn.watch, CVE.org
32.2 %
EPSS score
Elevated — model estimates 10-50% exploitation likelihood.
Source: FIRST EPSS, percentile 98.3
Show all metrics
- Severity
- Critical
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 217.55 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- actively exploitedSource: CSA/SingCERT How we classify
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 7.2 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 6.6
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 32.2 %
- Elevated — model estimates 10-50% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 98.3
- Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- Actively exploited
- Published
In CISA KEV since
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossaryCWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-78
Response and mitigation
Why act now?
Prioritisation rationale
Exploitation needs admin privileges, but the flaw sits in a platform that brokers privileged remote access to the rest of the estate. Stolen API keys, compromised admin accounts or an upstream authentication bypass turn it into direct code execution on the appliance, and from there a path to every connected system. Exploitation likelihood is very high, and CISA does not flag known ransomware use. Typical targets include government agencies, financial services, MSPs and critical-infrastructure operators. Organisations with an internet-facing RS/PRA instance should treat this as critical and patch within 24 hours; everyone else should patch at the next maintenance window, and no later than one week.
Runbook step 1
Immediate response (0-24 h)
- Inventory: Identify every BeyondTrust Remote Support (RS) and Privileged Remote Access (PRA) appliance, whether physical, virtual or cloud. Version 24.3.1 is confirmed affected. Check the running version in the
/applianceinterface. - Patch: A patch is available from the vendor. Look up the exact patch name and covered release branches in the BeyondTrust advisory. Update on-prem appliances via
/appliance→ Updates now. For cloud instances, get written confirmation of patch status from BeyondTrust support. - Rotate privileged access: Exploitation requires admin rights, so treat admin credentials as the attack surface. Rotate local admin accounts, review SAML/LDAP admin group mappings, and revoke and reissue all API keys (Configuration → API). Delete unused API accounts.
- Restrict the admin UI: Limit access to
/login(admin web interface, TCP 443) to management networks or jump hosts via firewall or reverse proxy. Remove any internet exposure of the admin interface immediately. - Compromise assessment: Review admin logins, newly created users and configuration changes over the last 90 days (see detection). If anything looks off, treat the appliance as compromised: preserve logs, engage vendor support, and assess NIS2 reporting obligations.
- Inventory: Identify every BeyondTrust Remote Support (RS) and Privileged Remote Access (PRA) appliance, whether physical, virtual or cloud. Version 24.3.1 is confirmed affected. Check the running version in the
Runbook step 2
Mitigation layers
- Network segmentation: Place RS/PRA appliances in a dedicated DMZ zone. Allow only required egress (vendor update servers, Jump Clients, SIEM) and block and log everything else to stop reverse shells and exfiltration.
- IAM / least privilege: Cut the number of admin-capable accounts to the minimum. Enforce MFA on all admin logins and use just-in-time elevation. Scope API keys to minimal permissions and bind them to source IPs.
- Reverse proxy / WAF: Only permit file uploads to admin paths from approved source IPs. Block and alert on multipart uploads to admin endpoints containing shell metacharacters (
;,|,`,$() in filenames or fields. - Configuration hardening: Disable unused features such as the API or unneeded auth providers. Enable syslog forwarding to the central SIEM so evidence survives an on-box compromise.
- If you can't patch yet: Take the admin interface off the internet entirely. Allow access only through MFA-protected VPN and actively monitor admin sessions. Record this as a formal risk exception in the ISMS.
Runbook step 3
Detection rules
- Admin authentication (appliance syslog/SIEM): Flag successful admin logins from unfamiliar source IPs or outside business hours. SPL sketch:
index=beyondtrust (event="login" role="admin") | stats dc(src_ip) values(src_ip) by user | where dc(src_ip)>2 - API abuse: Look for sudden API key usage, newly created API accounts, or token requests (
/oauth2/token) from non-allowlisted IPs. Sigma shape: selectionuri|contains: '/oauth2/token', filtered against known integration IPs. - Configuration and upload events: Investigate file uploads or admin UI changes (branding, plugins, file store) with no matching change ticket. In web access logs, hunt for
POSTrequests to admin paths withmultipart/form-datafrom atypical clients. - Network telemetry (Zeek/Suricata): Watch for new outbound connections from the appliance to unknown destinations, especially odd ports or long-lived sessions that suggest a reverse shell. KQL sketch:
CommonSecurityLog | where SourceIP in (bt_appliances) and DestinationIP !in (allowlist) | summarize count() by DestinationIP, DestinationPort - Downstream activity: Look for unusual Jump Client sessions, password resets, or endpoint process chains with the BeyondTrust client as parent (
bomgar-scc.exe→cmd.exe/powershell.exe, Sysmon EID 1) outside approved support windows.
- Admin authentication (appliance syslog/SIEM): Flag successful admin logins from unfamiliar source IPs or outside business hours. SPL sketch:
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
A vulnerability has been discovered in Privileged Remote Access (PRA) and Remote Support (RS) which can allow an attacker with existing administrative privileges to inject commands and run as a site user.
Source: CSA/SingCERT, pwn.watch, NVD (NIST), cvelistv5, CISA KEV Catalog, CVE.org (MITRE)
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| BeyondTrust | Remote Support(RS) & Privileged Remote Access(PRA) |
|
|
| beyondtrust | privileged_remote_access |
|
|
| beyondtrust | remote_support |
|
|
Vendors and products
Weakness classes (CWE)
CWE-78Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Base
The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.
Entry at MITRE CWE-78
Public exploit references
Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.
| CISA KEV Catalog | CISA Known Exploited Vulnerability (opens in a new tab)cisa.gov | actively exploited | |
| CSA/SingCERT | Vulnerabilities in BeyondTrust Products (opens in a new tab)CSA/SingCERT | actively exploited |
References & sources
- NVD (NIST)NVD: CVE-2024-12686Third-party advisory, US government resource, pwn-watch
- beyondtrust.comBeyondTrust advisory: BeyondTrust Privileged Remote Access (PRA) and Remote Support (RS)Vendor advisory, pwn-watch
- cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2024-12686government-resource, US government resource
- pwn.watchpwn.watch: BeyondTrust Privileged Remote Access (PRA) and Remote Support (RS): Privileged Remote Access (PRA) and Remote Support (RS) OS Command Injection Vulnerabilitypwn-watch
- cisa.govCISA Known Exploited Vulnerabilities Catalogpwn-watch
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2024-12686"><img src="https://intel.neosec.eu/badge/cve/CVE-2024-12686.svg?lang=en" alt="CVE-2024-12686 – NEOSEC Intel" height="20"></a>