CriticalCVE-2024-43468

    Microsoft Configuration Manager Remote Code Execution Vulnerability (CVE-2024-43468)

    Published In CISA KEV since Sources: SingCERT, CVE.org, Msrc Update Guide

    What is affected, what to do

    Microsoft Configuration Manager Remote Code Execution Vulnerability

    The vulnerability is being actively exploited; treat it as a priority. Update Microsoft Configuration Manager to version 5.00.9106. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Microsoft Configuration Manager lt 1.0.0..5.00.9106
    Fixed in
    • Microsoft Configuration Manager 5.00.9106

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    9.8

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    9.8

    CVSS v3

    Severity Critical on the scale from 0 to 10.

    Source: SingCERT, CVE.org, Msrc Update Guide

    81.0 %

    EPSS score

    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.

    Source: FIRST EPSS, percentile 99.63

    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
    234.91 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 exploited
    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
    9.8 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
    9.8
    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
    81.0 %
    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
    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
    99.63
    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 glossary
    CWE

    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-89

    Response and mitigation

    Why act now?

    Prioritisation rationale

    This flaw yields pre-authenticated remote code execution on a Tier-0 management system whose legitimate purpose is to execute code on virtually every Windows endpoint in the organisation — successful exploitation is effectively fleet-wide admin access, making it a direct ransomware and wiper enabler even though CISA has not (yet) flagged known ransomware use. The CVSS vector (network-reachable, no authentication, no user interaction) combined with a very high exploitation likelihood puts this CVE ahead of classic edge-device fixes in the queue. For NIS2-scoped organisations that rely on ConfigMgr for software distribution this qualifies as a "critical incident with potentially significant impact" — patch SLA 24-72 h, immediate if any Management Point is internet-exposed.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Deploy the Microsoft patch for CVE-2024-43468 without delay: upgrade Configuration Manager to build 5.00.9106 (hotfix KB29166583 / rollup per MSRC advisory) or later across branches 2403, 2409 and 2503. Prioritise the site server and all SMS Provider hosts.
      • Temporarily block network access to SMS Provider and Management Point roles from any non-administrative subnet (HTTPS/TCP 443, HTTP/TCP 80, SMB/TCP 445, plus SQL back-ends on TCP 1433/1434 and named instances). Allow only from the admin jump-host segment.
      • Rotate the SQL service account used by the ConfigMgr site server as well as all stored credentials: Network Access Account, Client Push Install Account, Reporting Services Point account. On confirmed compromise, also reissue the site system certificate.
      • Audit the site database (CM_) for unexpected sysadmin logins, new linked servers and the state of xp_cmdshell; if enabled and not required: EXEC sp_configure 'xp_cmdshell', 0; RECONFIGURE;.
      • Open an incident ticket scoped as "Tier-0 system" — ConfigMgr drives software deployment to every managed endpoint, so a compromise is a supply-chain risk into the entire estate.

    2. Runbook step 2

      Mitigation layers

      • Network segmentation: place the site server, SQL back-end and SMS Provider in a dedicated management VLAN; permit inbound traffic only from admin workstations following the PAW model. Restrict outbound internet access from the site server to Microsoft update FQDNs on a deny-by-default basis.
      • WAF / reverse proxy in front of Management Points, with rules targeting SQLi patterns in SOAP and HTTP POST bodies against ConfigMgr client endpoints (/ccm_system/, /ccm_system_windowsauth/, /CCM_Incoming/, /sms_mp/.sms_aut). Block payloads containing UNION SELECT, xp_cmdshell, ;-- or hex-encoded SQL keywords.
      • SQL hardening: constrain the site server's DB service account to the minimum roles the product requires (no gratuitous sysadmin), disable xp_cmdshell, enable SQL audit on FAILED_LOGIN_GROUP and SCHEMA_OBJECT_CHANGE_GROUP.
      • Endpoint hardening on the site server: AppLocker / WDAC policy that denies cmd.exe and powershell.exe spawned by the SQL Server process (sqlservr.exe) and IIS worker (w3wp.exe). Enable LSA Protection and Credential Guard.
      • IAM: dedicated admin accounts for the ConfigMgr Full Administrator role, enforce MFA via Entra ID Conditional Access, restrict use to PAWs. No shared service accounts between ConfigMgr and other products.
      • Monitoring baseline: snapshot the current site configuration (boundaries, collections, scripts, applications) so later tampering by a persistent attacker becomes detectable.

    3. Runbook step 3

      Detection rules

      • SQL Server audit: alert on new logins granted sysadmin or on sp_addsrvrolemember calls inside CM_. KQL shape: SecurityEvent | where EventID == 33205 and AuditData has_any ("xp_cmdshell","sp_configure","sp_addsrvrolemember").
      • Sysmon EID 1 on the site server and SQL host: process-ancestry chains sqlservr.exe -> cmd.exe|powershell.exe|rundll32.exe|certutil.exe or w3wp.exe -> cmd.exe are extremely rare in a healthy ConfigMgr environment and warrant a high-severity alert.
      • IIS access logs on Management Points: POST requests against /ccm_system/ or /sms_mp/.sms_aut with unusually large bodies, SQL keywords in the URL-decoded payload or user-agents outside the known ConfigMgr clients. Sigma shape: selection: cs-uri-stem|contains: '/ccm_system' AND cs-method: POST AND cs(User-Agent)|not_contains: 'SMS CCM'.
      • Windows Event IDs 4688/4624 on the site server: unexpected logons of the SQL service account, interactive or network, outside maintenance windows; Event IDs 4720/4732 for newly created local administrators.
      • Network telemetry (Zeek/Suricata): abnormal HTTP response sizes from the Management Point to individual client IPs (data exfiltration via query response) and SMB connections from the site server toward hosts not managed by ConfigMgr.

    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

    Microsoft Configuration Manager Remote Code Execution Vulnerability

    Source: CSA/SingCERT, NVD (NIST), Microsoft Security Update Guide, 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 products
    Affected versionsFixed in
    MicrosoftMicrosoft Configuration Manager
    • 1.0.0 – < 5.00.9106
    • 5.00.9106
    microsoftconfiguration_manager_2403
    • —
    • —
    microsoftconfiguration_manager_2409
    • —
    • —
    microsoftconfiguration_manager_2503
    • —
    • —

    Vendors and products

    Weakness classes (CWE)

    • CWE-89Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

      Base

      The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

      Entry at MITRE CWE-89

    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.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited

    References & sources

    • Microsoft Security Update GuideMicrosoft Configuration Manager Remote Code Execution VulnerabilityVendor advisory, Patch, Vendor advisory
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2024-43468government-resource, US government resource
    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2024-43468
    <a href="https://intel.neosec.eu/en/cve/CVE-2024-43468"><img src="https://intel.neosec.eu/badge/cve/CVE-2024-43468.svg?lang=en" alt="CVE-2024-43468 – NEOSEC Intel" height="20"></a>