Important CVSS 7.8 EPSS 0.05722 🔬 Patch diffed 2024-08 archive

Executive Summary

None

Overview

7.8
CVSS HIGH
Important
MS Severity
Not Exploited
MS Exploit Status
More Likely
MS Exploit Likelihood
Category Elevation of Privilege
Released Aug 13 2024
Last Updated Aug 13 2024
Publicly Disclosed No
CISA KEV Not Listed
Known Exploits None Known
EPSS Score 0.05722 — 0.92361 percentile
NVD CVSS 7.8 HIGH — matches MSRC

CVSS Vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
ATTACK VECTOR
Local
ATTACK COMPLEXITY
Low
PRIVILEGES REQUIRED
Low
USER INTERACTION
None
SCOPE
Unchanged
CONFIDENTIALITY
High
INTEGRITY
High
AVAILABILITY
High
EXPLOIT CODE MATURITY
Unproven
REMEDIATION LEVEL
Official Fix
REPORT CONFIDENCE
Confirmed
Temporal Score: 6.8

EPSS Score

0.05722
probability of exploitation in the next 30 days
0.92361 percentile - updated 2026-08-14
View on FIRST.org

Affected Products

31 affected products
Product KB Article Severity Impact Restart Required
Windows 10 for 32-bit Systems 5041782 (Security Update) Important Elevation of Privilege Yes
Windows 10 for x64-based Systems 5041782 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 1607 for 32-bit Systems 5041773 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 1607 for x64-based Systems 5041773 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 1809 for 32-bit Systems 5041578 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 1809 for x64-based Systems 5041578 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 21H2 for 32-bit Systems 5041580 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 21H2 for ARM64-based Systems 5041580 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 21H2 for x64-based Systems 5041580 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 22H2 for 32-bit Systems 5041580 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 22H2 for ARM64-based Systems 5041580 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 22H2 for x64-based Systems 5041580 (Security Update) Important Elevation of Privilege Yes
Windows 11 version 21H2 for ARM64-based Systems 5041592 (Security Update) Important Elevation of Privilege Yes
Windows 11 version 21H2 for x64-based Systems 5041592 (Security Update) Important Elevation of Privilege Yes
Windows 11 Version 22H2 for ARM64-based Systems 5041585 (Security Update) Important Elevation of Privilege Yes
Windows 11 Version 22H2 for x64-based Systems 5041585 (Security Update) Important Elevation of Privilege Yes
Windows 11 Version 23H2 for ARM64-based Systems 5041585 (Security Update) Important Elevation of Privilege Yes
Windows 11 Version 23H2 for x64-based Systems 5041585 (Security Update) Important Elevation of Privilege Yes
Windows 11 Version 24H2 for ARM64-based Systems 5041571 (Security Update) Important Elevation of Privilege Yes
Windows 11 Version 24H2 for x64-based Systems 5041571 (Security Update) Important Elevation of Privilege Yes
Windows Server 2008 for 32-bit Systems Service Pack 2 5041850 (Monthly Rollup) 5041847 (Security Only) Important Elevation of Privilege 5040499 Base: 7.8 Temporal: 6.8 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 6.0.6003.22825 Yes 5041850 5041847 Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation) 5041850 (Monthly Rollup) 5041847 (Security Only) Important Elevation of Privilege 5040499 Base: 7.8 Temporal: 6.8 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 6.0.6003.22825 Yes 5041850 5041847 Windows Server 2008 for x64-based Systems Service Pack 2 5041850 (Monthly Rollup) 5041847 (Security Only) Important Elevation of Privilege 5040499 Base: 7.8 Temporal: 6.8 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 6.0.6003.22825 Yes 5041850 5041847 Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation) 5041850 (Monthly Rollup) 5041847 (Security Only) Important Elevation of Privilege 5040499 Base: 7.8 Temporal: 6.8 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 6.0.6003.22825 Yes 5041850 5041847 Windows Server 2008 R2 for x64-based Systems Service Pack 1 5041838 (Monthly Rollup) 5041823 (Security Only) Important Elevation of Privilege 5040497 Base: 7.8 Temporal: 6.8 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 6.1.7601.27277 Yes 5041838 Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation) 5041838 (Monthly Rollup) 5041823 (Security Only) Important Elevation of Privilege 5040497 Base: 7.8 Temporal: 6.8 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 6.1.7601.27277 Yes 5041838 Windows Server 2012 5041851 (Monthly Rollup) Important Elevation of Privilege Yes
Windows Server 2012 (Server Core installation) 5041851 (Monthly Rollup) Important Elevation of Privilege Yes
Windows Server 2012 R2 5041828 (Monthly Rollup) Important Elevation of Privilege Yes
Windows Server 2012 R2 (Server Core installation) 5041828 (Monthly Rollup) Important Elevation of Privilege Yes
Windows Server 2016 5041773 (Security Update) Important Elevation of Privilege Yes
Windows Server 2016 (Server Core installation) 5041773 (Security Update) Important Elevation of Privilege Yes
Windows Server 2019 5041578 (Security Update) Important Elevation of Privilege Yes
Windows Server 2019 (Server Core installation) 5041578 (Security Update) Important Elevation of Privilege Yes
Windows Server 2022 5041160 (Security Update) Important Elevation of Privilege Yes
Windows Server 2022 (Server Core installation) 5041160 (Security Update) Important Elevation of Privilege Yes
Windows Server 2022, 23H2 Edition (Server Core installation) 5041573 (Security Update) Important Elevation of Privilege Yes

Patches

11 patches
Article Type Restart
5041782 Security Update Yes
5041773 Security Update Yes
5041578 Security Update Yes
5041580 Security Update Yes
5041592 Security Update Yes
5041585 Security Update Yes
5041571 Security Update Yes
5041851 Monthly Rollup Yes
5041828 Monthly Rollup Yes
5041160 Security Update Yes
5041573 Security Update Yes

Patch Diff

ghidriff · clfs.sys (KB5041571)

Improper input validation (CWE-20) in the Windows Common Log File System driver clfs.sys base-log-file (.blf) metadata parsing, local EoP to SYSTEM. CLFS parses a base log file's control record, client contexts, container contexts and symbol tables - a structure full of self-referential offsets. PRE: the offset/length fields in the base-file metadata were not fully validated, so a crafted .blf could point offsets outside the valid region (symbol zone) and drive out-of-bounds access when CLFS resolves them (OffsetToAddr / GetSymbol / GetControlRecord). Diff of clfs.sys 10.0.26100.1301 -> .1455 (Aug 13 2024, KB5041571) confirms the fix: gated behind CFR flags Feature_110180665 / Feature_1868496191 / Feature_2458037564, CLFS adds/strengthens offset validation across the base-file parsers - ValidateOffsets, ValidateRgOffsets, ValidateClientContextOffsets, ValidateContainerContextOffsets and ValidateProcessQNode now bound each offset within the symbol zone (ValidateCheckifWithinSymbolZone) and cross-check the symbol length markers before OffsetToAddr resolves them, so a malformed .blf is rejected rather than parsed out of bounds.

Pre-patch version 10.0.26100.1301 Download
Post-patch version 10.0.26100.1455 Download
Function Address Change Note
CClfsBaseFile::ValidateClientContextOffsets code change code (client-context offsets validated against symbol zone) Post: walks each client-context offset (param_2+idx*4+0x138), requires it in-range via ValidateCheckifWithinSymbolZone, resolves with OffsetToAddr, and cross-checks the symbol length fields (*(pv-0xc)/*(pv-0x10)) before use.
CClfsBaseFile::ValidateContainerContextOffsets / ValidateOffsets / ValidateRgOffsets / ValidateProcessQNode code change code (offset validation strengthened) The container-context, region and process-QNode offset validators are hardened with the same in-symbol-zone bounds checks.
CClfsBaseFile::OffsetToAddr / GetSymbol / GetControlRecord / CClfsBaseFilePersisted::OpenImage/CreateImage code change code (base-file open/resolve paths updated) Offset-resolution and base-file open/create paths updated to use the validated offsets.
Feature_110180665 / Feature_1868496191 / Feature_2458037564 gate added (CFR gate) CFR flags gating the strengthened .blf offset validation; the original under-validating parser still ships when disabled.
View full diff report View RCA report

Root Cause Analysis

CVE-2024-38196 — Windows Common Log File System clfs.sys Under-Validated Base-Log-File Offsets → Improper Input Validation


Summary

Product Windows — clfs.sys (Common Log File System driver)
CVE ID CVE-2024-38196
Impact Elevation of Privilege (to SYSTEM)
MSRC severity Important
CVSS 7.8 / 6.8 — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
CWE CWE-20: Improper Input Validation
Delivery Local — a crafted CLFS base log file (.blf)
KB / Fixed build KB5041571 — clfs.sys 10.0.26100.1455 (Win11 24H2 x64)
Patch Date August 13, 2024 (2024-Aug)
Pre-patch binary clfs.sys 10.0.26100.1301 — SHA256 12ea662173adb00e038c8d9403e749ed73fb09b752a58430c8518eb670f0fe0b
Post-patch binary clfs.sys 10.0.26100.1455 — SHA256 b1782f78ca4f26082d331c269a7a3e554461963016746502efea481ff9cc3b13
Feature flag Feature_110180665 / Feature_1868496191 / Feature_2458037564 — CFR-gated
Exploitability Exploitation More Likely; not publicly disclosed; not exploited (per MSRC)

Sourcing note: the OS fixed build is .1457; the clfs.sys binary in KB5041571 is versioned .1455. Pre = .1301.


Product Description

clfs.sys is the Common Log File System driver. A base log file (.blf) holds a control record plus client contexts, container contexts and symbol tables — a structure full of self-referential offsets that CLFS resolves (OffsetToAddr, GetSymbol, GetControlRecord) when opening/parsing the log (CClfsBaseFilePersisted::OpenImage / CreateImage). CLFS .blf parsing is a long-standing local EoP attack surface because a user can supply a crafted log file.


Vulnerability Summary

Pre-patch, the offset/length fields in the base-file metadata were not fully validated before use. A crafted .blf could set client-context / container-context / region offsets that point outside the valid region (symbol zone), so when CLFS resolved them (OffsetToAddr → the referenced structure) it accessed memory out of bounds — improper input validation (CWE-20) of attacker-controlled log metadata, exploitable for local elevation of privilege to SYSTEM (Microsoft rates exploitation More Likely).


Prerequisites and Constraints

  • Local, low-privileged (PR:L, AV:L, AC:L): create/open a crafted CLFS base log file.
  • Set metadata offsets to reference locations outside the valid symbol zone.
  • Result: CLFS resolves an out-of-range offset while parsing the log.

Vulnerability Details

Root Cause

The many self-referential offsets in the base-file control record / client & container contexts were resolved without fully bounding them within the file’s valid region, so a malformed .blf produced out-of-bounds accesses.

The patch (confirmed — diff, .1301 → .1455)

Gated behind Feature_110180665 / Feature_1868496191 / Feature_2458037564, CLFS adds/strengthens offset validation across the base-file parsers — the Validate*Offsets routines now bound each offset within the symbol zone and cross-check the symbol length markers before OffsetToAddr resolves them:

// CClfsBaseFile::ValidateClientContextOffsets (10.0.26100.1455) — PATCHED (from our diff)
while (idx < 0x7c) {
    off = *(uint *)(param_2 + idx*4 + 0x138);
    if (off - 1 < 0xfffffffe) {
        if (ValidateCheckifWithinSymbolZone(this, off + 0x87, param_2) < 0) goto reject;  // *** bound in symbol zone ***
        pv = OffsetToAddr(this, ...);
        if (pv == NULL) goto reject;
        if (*(int *)(pv - 0xc) != off || *(int *)(pv - 0x10) != *(int *)(pv - 0xc) + 0x88)  // *** cross-check length markers ***
            goto reject;
    }
    ...
}

The same in-symbol-zone bounds discipline is applied in ValidateContainerContextOffsets, ValidateOffsets, ValidateRgOffsets and ValidateProcessQNode, so a malformed .blf is rejected rather than parsed out of bounds.

Patch Completeness Assessment

CFR-gated behind Feature_110180665 / Feature_1868496191 / Feature_2458037564. The strengthened validation runs only when the flags are enabled; the original under-validating parser still ships when disabled. Verify the flags are enabled to confirm the fix is live.


Detection Guidance

Behavioural. Opening/creating CLFS base log files (.blf) with offset/length fields that reference outside the file’s structures; OOB / pool-corruption bugchecks in clfs!CClfsBaseFile::OffsetToAddr / GetSymbol / Validate*Offsets on unpatched/flag-disabled builds. CLFS .blf abuse is a common local-EoP technique — monitor untrusted .blf creation.

Config. The fix is CFR-gated — confirm the three flags are enabled.


References

  • MSRC advisory — CVE-2024-38196 (Windows Common Log File System Driver Elevation of Privilege), released 2024-08-13, KB5041571.
  • Full binary diff: /data/patch_diffs/clfs_sys-cve-2024-38196-ghidriff.md

Attack Path

A crafted CLFS base log file (.blf) supplies offsets outside the valid region, driving out-of-bounds access on parse

Attack path for CVE-2024-38196 A crafted CLFS base log file (.blf) supplies offsets outside the valid region, driving out-of-bounds access on parse 01 — ENTRY Local user opens/creates a crafted CLFS base log file (.blf) clfs.sys parses the control record / client & container contexts / symbol tables. AV:L/PR:L/AC:L. 02 — CONTROLLED INPUT Sets metadata offsets to point outside the valid symbol zone Self-referential offset/length fields in the .blf are attacker-controlled. 03 — MISSING CHECK Offsets not fully validated before resolution (CWE-20) OffsetToAddr / GetSymbol resolve an out-of-range offset from the malformed base file. 04 — PATH Out-of-bounds access on CLFS metadata The bad offset yields OOB read/write while parsing the log structures in the kernel. 05 — PRIMITIVE Improper input validation -> OOB -> EoP to SYSTEM The Aug 2024 fix bounds each offset within the symbol zone (ValidateCheckifWithinSymbolZone) and cross-checks length markers before use.

Derived from the patch delta: the checks added by the vendor identify which fields crossed a trust boundary unvalidated. Reachability and privilege are taken from the call chain in the RCA report.

Exploits & PoC

Detection Rules

Acknowledgments

luckyu with MatrixCup
Anonymous