LiveActive security incident?Get immediate response
CVE Record

CVE-2024-38263: Windows Remote Desktop Licensing Service Remote Code Execution Vulnerability

Windows Remote Desktop Licensing Service Remote Code Execution Vulnerability

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A flaw in Windows Remote Desktop Licensing Service could let a low-privileged attacker execute code remotely on affected Windows Server systems. A successful attack could expose data, alter the server, or disrupt operations. Exploitation is rated high complexity, so this is serious but not classified as critical.

Executive priority

Prioritize remediation for reachable Remote Desktop Licensing servers, especially systems accessible from untrusted networks. Schedule prompt patching after operational validation. Although exploitation requires low privileges and high complexity, the potential consequence is complete compromise of confidentiality, integrity, and availability.

Technical view

CVE-2024-38263 is a network-accessible remote code execution vulnerability assigned CWE-591. CVSS 3.1 rates it 7.5: high complexity, low privileges required, no user interaction, unchanged scope, and high confidentiality, integrity, and availability impact. The supplied sources do not describe the underlying mechanism or exact exploitation prerequisites.

Likely exposure

Exposure is most likely on listed Windows Server 2008 through 2022 and 23H2 Server Core systems where Remote Desktop Licensing Service is installed, reachable, and missing the applicable Microsoft update. The bundle does not establish that every affected-version server is exploitable by default.

Exploitation context

The supplied evidence does not establish active exploitation or public exploit availability. The KEV flag is false, and the CVSS exploit-maturity metric is unproven. High attack complexity and required low privileges reduce likelihood, but successful exploitation could fully compromise the service host.

Researcher notes

The bundle identifies CWE-591 but provides no root-cause detail, affected function, protocol behavior, or proof-of-concept evidence. Avoid inferring a memory-corruption mechanism or specific attack path. Exact fixed builds and update identifiers must be obtained from the Microsoft advisory.

Mitigation direction

  • Inventory affected Windows Server versions and Remote Desktop Licensing Service deployments.
  • Apply the applicable Microsoft security update identified by the MSRC advisory.
  • If patching is delayed, restrict licensing-service access to required trusted systems.
  • Monitor the Microsoft advisory for revised affected-version or remediation information.

Validation and detection

  • Match each server product, edition, and build against the supplied affected list.
  • Confirm whether Remote Desktop Licensing Service is installed, active, and network-reachable.
  • Verify the applicable Microsoft security update is installed successfully.
  • Reassess exposed systems using an authenticated vulnerability or patch-management scan.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-591: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-38263 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C1.65.9microsoft

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2024-38263Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftWindows Server 2008 Service Pack 26.0.6003.0Listed
MicrosoftWindows Server 2008 R2 Service Pack 16.1.7601.0Listed
MicrosoftWindows Server 2008 R2 Service Pack 1 (Server Core installation)6.1.7601.0Listed
MicrosoftWindows Server 2008 Service Pack 26.0.6003.0Listed
MicrosoftWindows Server 2008 Service Pack 2 (Server Core installation)6.0.6003.0Listed
MicrosoftWindows Server 20126.2.9200.0Listed
MicrosoftWindows Server 2012 (Server Core installation)6.2.9200.0Listed
MicrosoftWindows Server 2012 R26.3.9600.0Listed
MicrosoftWindows Server 2012 R2 (Server Core installation)6.3.9600.0Listed
MicrosoftWindows Server 201610.0.14393.0Listed
MicrosoftWindows Server 2016 (Server Core installation)10.0.14393.0Listed
MicrosoftWindows Server 201910.0.17763.0Listed
MicrosoftWindows Server 2019 (Server Core installation)10.0.17763.0Listed
MicrosoftWindows Server 202210.0.20348.0Listed
MicrosoftWindows Server 2022, 23H2 Edition (Server Core installation)10.0.25398.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-591 · source CWE mapping

Sensitive Data Storage in Improperly Locked Memory

Sensitive Data Storage in Improperly Locked Memory represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.