msrc.microsoft.com
Open in
urlscan Pro
2620:1ec:bdf::40
Public Scan
Submitted URL: http://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-38077
Effective URL: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-38077
Submission: On August 12 via api from DE — Scanned from US
Effective URL: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-38077
Submission: On August 12 via api from DE — Scanned from US
Form analysis
0 forms found in the DOMText Content
You need to enable JavaScript to run this app. Skip to main contentMicrosoft MSRC Security Updates Acknowledgements Feedback and Support Sign in to your account Sign in 1. MSRC MSRC 2. Customer Guidance Customer Guidance 3. Security Update Guide Security Update Guide 4. Vulnerabilities Vulnerabilities 5. CVE 2024 38077 CVE 2024 38077 WINDOWS REMOTE DESKTOP LICENSING SERVICE REMOTE CODE EXECUTION VULNERABILITY On this page CVE-2024-38077 Subscribe RSS PowerShell API Security Vulnerability Released: Jul 8, 2024 Assigning CNA: Microsoft CVE-2024-38077 Impact: Remote Code Execution Max Severity: Critical Weakness: CWE-122: Heap-based Buffer Overflow CVSS Source: Microsoft CVSS:3.1 9.8 / 8.5 Base score metrics: 9.8 / Temporal score metrics: 8.5 Base score metrics: 9.8 / Temporal score metrics: 8.5 Expand all Collapse all Metric Value Base score metrics(8) Attack Vector This metric reflects the context by which vulnerability exploitation is possible. The Base Score increases the more remote (logically, and physically) an attacker can be in order to exploit the vulnerable component. Network The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers). Attack Complexity This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability. Such conditions may require the collection of more information about the target or computational exceptions. The assessment of this metric excludes any requirements for user interaction in order to exploit the vulnerability. If a specific configuration is required for an attack to succeed, the Base metrics should be scored assuming the vulnerable component is in that configuration. Low Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component. Privileges Required This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability. None The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack. User Interaction This metric captures the requirement for a user, other than the attacker, to participate in the successful compromise the vulnerable component. This metric determines whether the vulnerability can be exploited solely at the will of the attacker, or whether a separate user (or user-initiated process) must participate in some manner. None The vulnerable system can be exploited without any interaction from any user. Scope Does a successful attack impact a component other than the vulnerable component? If so, the Base Score increases and the Confidentiality, Integrity and Authentication metrics should be scored relative to the impacted component. Unchanged An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority. Confidentiality This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability. Confidentiality refers to limiting information access and disclosure to only authorized users, as well as preventing access by, or disclosure to, unauthorized ones. High There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. Integrity This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information. High There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component. Availability This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability. It refers to the loss of availability of the impacted component itself, such as a networked service (e.g., web, database, email). Since availability refers to the accessibility of information resources, attacks that consume network bandwidth, processor cycles, or disk space all impact the availability of an impacted component. High There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable). Temporal score metrics(3) Exploit Code Maturity This metric measures the likelihood of the vulnerability being attacked, and is typically based on the current state of exploit techniques, public availability of exploit code, or active, 'in-the-wild' exploitation. Unproven No publicly available exploit code is available, or an exploit is theoretical. Remediation Level The Remediation Level of a vulnerability is an important factor for prioritization. The typical vulnerability is unpatched when initially published. Workarounds or hotfixes may offer interim remediation until an official patch or upgrade is issued. Each of these respective stages adjusts the temporal score downwards, reflecting the decreasing urgency as remediation becomes final. Official Fix A complete vendor solution is available. Either the vendor has issued an official patch, or an upgrade is available. Report Confidence This metric measures the degree of confidence in the existence of the vulnerability and the credibility of the known technical details. Sometimes only the existence of vulnerabilities are publicized, but without specific details. For example, an impact may be recognized as undesirable, but the root cause may not be known. The vulnerability may later be corroborated by research which suggests where the vulnerability may lie, though the research may not be certain. Finally, a vulnerability may be confirmed through acknowledgement by the author or vendor of the affected technology. The urgency of a vulnerability is higher when a vulnerability is known to exist with certainty. This metric also suggests the level of technical knowledge available to would-be attackers. Confirmed Detailed reports exist, or functional reproduction is possible (functional exploits may provide this). Source code is available to independently verify the assertions of the research, or the author or vendor of the affected code has confirmed the presence of the vulnerability. Please see Common Vulnerability Scoring System for more information on the definition of these metrics. EXPLOITABILITY The following table provides an exploitability assessment for this vulnerability at the time of original publication. Publicly disclosedNoExploitedNoExploitability assessmentExploitation Less Likely MITIGATIONS The following mitigation may be helpful in your situation. In all cases, Microsoft strongly recommends that you install the updates for this vulnerability as soon as possible even if you plan to leave Remote Desktop Licensing Service disabled: 1. Disable Remote Desktop Licensing Service if is not required. If you no longer need this service on your system, consider disabling it as a security best practice. Disabling unused and unneeded services helps reduce your exposure to security vulnerabilities. FAQ How would an attacker exploit this vulnerability? An unauthenticated attacker could connect to the Remote Desktop Licensing Service and send a malicious message which could allow remote code execution. ACKNOWLEDGEMENTS * Lewis Lee, Chunyang Han and Zhiniang Peng Microsoft recognizes the efforts of those in the security community who help us protect customers through coordinated vulnerability disclosure. See Acknowledgements for more information. SECURITY UPDATES To determine the support lifecycle for your software, see the Microsoft Support Lifecycle. Updates CVSS Release date Descending Edit columns Download Filters Release date Product Platform Impact Max Severity Article Download Build Number Jul 8, 2024 Windows Server 2012 R2 (Server Core installation) - Remote Code Execution Critical * 5040456 * Monthly Rollup * 6.3.9600.22074 Jul 8, 2024 Windows Server 2012 R2 - Remote Code Execution Critical * 5040456 * Monthly Rollup * 6.3.9600.22074 Jul 8, 2024 Windows Server 2012 (Server Core installation) - Remote Code Execution Critical * 5040485 * Monthly Rollup * 6.2.9200.24975 Jul 8, 2024 Windows Server 2012 - Remote Code Execution Critical * 5040485 * Monthly Rollup * 6.2.9200.24975 Jul 8, 2024 Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation) - Remote Code Execution Critical * 5040497 * 5040498 * Monthly Rollup * Security Only * 6.1.7601.27219 * 6.1.7601.27219 Jul 8, 2024 Windows Server 2008 R2 for x64-based Systems Service Pack 1 - Remote Code Execution Critical * 5040497 * 5040498 * Monthly Rollup * Security Only * 6.1.7601.27219 * 6.1.7601.27219 Jul 8, 2024 Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation) - Remote Code Execution Critical * 5040499 * 5040490 * Monthly Rollup * Security Only * 6.0.6003.22769 * 6.0.6003.22769 Jul 8, 2024 Windows Server 2008 for x64-based Systems Service Pack 2 - Remote Code Execution Critical * 5040499 * 5040490 * Monthly Rollup * Security Only * 6.0.6003.22769 * 6.0.6003.22769 Jul 8, 2024 Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation) - Remote Code Execution Critical * 5040499 * 5040490 * Monthly Rollup * Security Only * 6.0.6003.22769 * 6.0.6003.22769 Jul 8, 2024 Windows Server 2008 for 32-bit Systems Service Pack 2 - Remote Code Execution Critical * 5040499 * 5040490 * Monthly Rollup * Security Only * 6.0.6003.22769 * 6.0.6003.22769 Jul 8, 2024 Windows Server 2016 (Server Core installation) - Remote Code Execution Critical * 5040434 * Security Update * 10.0.14393.7159 Jul 8, 2024 Windows Server 2016 - Remote Code Execution Critical * 5040434 * Security Update * 10.0.14393.7159 Jul 8, 2024 Windows Server 2022, 23H2 Edition (Server Core installation) - Remote Code Execution Critical * 5040438 * Security Update * 10.0.25398.1009 Jul 8, 2024 Windows Server 2022 (Server Core installation) - Remote Code Execution Critical * 5040437 * Security Update * 10.0.20348.2582 Jul 8, 2024 Windows Server 2022 - Remote Code Execution Critical * 5040437 * Security Update * 10.0.20348.2582 Jul 8, 2024 Windows Server 2019 (Server Core installation) - Remote Code Execution Critical * 5040430 * Security Update * 10.0.17763.6054 Jul 8, 2024 Windows Server 2019 - Remote Code Execution Critical * 5040430 * Security Update * 10.0.17763.6054 All results loaded Loaded all 17 rows DISCLAIMER The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply. REVISIONS version revisionDate description 1.0 Jul 8, 2024 Information published. How satisfied are you with the MSRC Security Update Guide? Rating Broken Bad Below average Average Great!