Code execution via improper object handling
Published May 10, 2022 · Updated Jan 2, 2025
Improper object handling in Microsoft Visual Studio 2017 before 15.9.48 allows local users to execute code after user interaction. Microsoft states only that Visual Studio improperly handles objects in memory and has not disclosed the affected parser, object type, or unsafe operation. Exploitation requires the current user to interact with attacker-controlled content, and successful code runs in that user's context.
Summary
What happened
Improper object handling in Microsoft Visual Studio 2017 before 15.9.48 allows local users to execute code after user interaction. Microsoft states only that Visual Studio improperly handles objects in memory and has not disclosed the affected parser, object type, or unsafe operation. Exploitation requires the current user to interact with attacker-controlled content, and successful code runs in that user's context.
The record
- CVE
- CVE-2022-29148
- Published
- May 10, 2022
- Updated
- Jan 2, 2025
- Vendor
- Microsoft
- Product
- Microsoft Visual Studio 2017
- Classifications
- T1204
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 10, 2022CVE publishedPublication date reported by the CVE source.
- Jan 2, 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=15.9.0 <15.9.48
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