CVE-2021-24084

SYSTEM file disclosure via directory junction

Published Feb 25, 2021 · Updated Aug 3, 2024

Information disclosure in Windows Device Management Enrollment Service allows local users to read arbitrary files with SYSTEM privileges. The service follows an attacker-created directory junction and returns contents from an unintended filesystem path rather than the enrollment directory. Exploitation requires low-privileged code execution on an affected host; it exposes file contents readable as SYSTEM without reported modification or service interruption.

CVSS severity5.5
Medium
EPSS probability2.77%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Information disclosure in Windows Device Management Enrollment Service allows local users to read arbitrary files with SYSTEM privileges. The service follows an attacker-created directory junction and returns contents from an unintended filesystem path rather than the enrollment directory. Exploitation requires low-privileged code execution on an affected host; it exposes file contents readable as SYSTEM without reported modification or service interruption.

The record

CVE
CVE-2021-24084
Published
Feb 25, 2021
Updated
Aug 3, 2024
Vendor
Microsoft
Product
Windows Server 2019
Classifications
CWE-59, CAPEC-132, T1005
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Feb 25, 2021CVE publishedPublication date reported by the CVE source.
  2. Aug 3, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=10.0.0 <10.0.17763.2366

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

Microsoft · Windows Server 2019version=10.0.0 <10.0.17763.2366
Microsoft · Windows 10 Version 1909version=10.0.0 <10.0.18363.1977
Microsoft · Windows Server, version 2004version=10.0.0 <10.0.19041.1415
Microsoft · Windows 10 Version 20H2version=10.0.0 <10.0.19042.1415
Microsoft · Windows Server 2019 (Server Core installation)version=10.0.0 <10.0.17763.2366
Microsoft · Windows Server version 20H2version=10.0.0 <10.0.19042.1415
Microsoft · Windows 10 Version 2004version=10.0.0 <10.0.19041.1415
Microsoft · Windows 10 Version 1809version=10.0.0 <10.0.17763.2366
Microsoft · Windows Server, version 1909 (Server Core installation)version=10.0.0 <publication

Published CVSS scores

5.5Microsoft CorporationCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
4.9NIST NVDAV:L/AC:L/Au:N/C:C/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-59Improper Link Resolution Before File Access ('Link Following')
CAPEC-132Symlink Attack
T1005Data from Local System

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo