CVE-2024-12356
A 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.
do firstApply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? Partly. Command injection puts shell syntax into the request. WAF rules catch common shell commands but miss encoded or unusual payloads.
Also consider: input validation · RASP
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2024-12356 being exploited?
Yes. CVE-2024-12356 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2024-12356?
CVE-2024-12356 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2024-12356?
Yes. A fix has been recorded for CVE-2024-12356. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2024-12356 affect?
CVE-2024-12356 affects beyondtrust:privileged_remote_access, beyondtrust:remote_support. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected<= 24.3.1
- affected<= 24.3.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
public exploits
Public exploit code: 1 Metasploit module · 1 GitHub proof of concept
- exploit/linux/http/beyondtrust_pra_rs_unauth_rce · exploit · excellent
- skraft9/CVE-2024-12356 · 2 ★
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- yes
- technical impact
- total
Assessed by CISA 19 Dec 2024 (SSVC 2.0.3).
timeline
- 17 Dec 2024Published
- 19 Dec 2024Added to CISA KEV (exploited in the wild) · 2 days later
- 19 Dec 2024CISA SSVC assessment: exploitation active · 1 day later
- 27 Dec 2024CISA remediation due date (US federal agencies) · 7 days later
- 21 Oct 2025CVE record last updated · 299 days (about 10 months) later
- 4 Sept 2026First public exploit or proof of concept · 317 days (about 11 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 60 days (about 2 months) later
- Linkcve.org /CVERecord?id=CVE-2024-12356
- Linknvd.nist.gov /vuln/detail/CVE-2024-12356
- Linkbeyondtrust.com /trust-center/security-advisories/bt24-10
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-12356
- Linkattackerkb.com /topics/G5s8ZWAbYH/cve-2024-12356/rapid7-analysis
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Metasploit Framework: exploit and scanner modules
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.