Code execution via unsafe deserialization
Published Feb 14, 2023 · Updated Aug 19, 2026
Unsafe deserialization in Microsoft SSIS Projects before 16.0.5035.3 allows local users to execute code after user interaction. The extension deserializes attacker-controlled data without sufficient validation, but Microsoft has not disclosed the affected file format, class, or function. Exploitation requires low-privilege local access and user interaction, and successful execution can compromise confidentiality, integrity, and availability.
Summary
What happened
Unsafe deserialization in Microsoft SSIS Projects before 16.0.5035.3 allows local users to execute code after user interaction. The extension deserializes attacker-controlled data without sufficient validation, but Microsoft has not disclosed the affected file format, class, or function. Exploitation requires low-privilege local access and user interaction, and successful execution can compromise confidentiality, integrity, and availability.
The record
- CVE
- CVE-2023-21568
- Published
- Feb 14, 2023
- Updated
- Aug 19, 2026
- Vendor
- Microsoft
- Product
- SQL Server Integration Services Projects for Visual Studio 2022
- Classifications
- CWE-502, T1204
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 14, 2023CVE publishedPublication date reported by the CVE source.
- Aug 19, 2026Record 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=16.0.0 <16.0.5035.3
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.
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