Privilege escalation via unrestricted BAML type instantiation
Published Jun 14, 2023 · Updated Jan 1, 2025
Type-instantiation weakness in WPF BAML in Microsoft .NET Framework allows local users to elevate privileges through a crafted file. The BAML loading path permits types to be instantiated through routes that bypass intended restrictions; Microsoft has not disclosed the specific parser method or type controls involved. Exploitation requires user interaction with the crafted file, after which code executes in the affected application's security context.
Summary
What happened
Type-instantiation weakness in WPF BAML in Microsoft .NET Framework allows local users to elevate privileges through a crafted file. The BAML loading path permits types to be instantiated through routes that bypass intended restrictions; Microsoft has not disclosed the specific parser method or type controls involved. Exploitation requires user interaction with the crafted file, after which code executes in the affected application's security context.
The record
- CVE
- CVE-2023-29326
- Published
- Jun 14, 2023
- Updated
- Jan 1, 2025
- Vendor
- Microsoft
- Product
- Microsoft .NET Framework 3.5 and 4.8.1
- Classifications
- T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 14, 2023CVE publishedPublication date reported by the CVE source.
- Jan 1, 2025Record 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.
- Affected versionversion=4.8.1 <4.8.9166.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
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