Code execution via undisclosed double-free condition
Published Oct 10, 2023 · Updated Apr 14, 2025
Double-free in Microsoft Azure RTOS GUIX Studio before 6.3.0 allows attackers to execute code after local user interaction. Microsoft identifies the weakness but has not published the affected function, parser, or input operation that releases memory twice. Exploitation requires user interaction, and successful exploitation runs attacker-controlled code in the GUIX Studio process.
Summary
What happened
Double-free in Microsoft Azure RTOS GUIX Studio before 6.3.0 allows attackers to execute code after local user interaction. Microsoft identifies the weakness but has not published the affected function, parser, or input operation that releases memory twice. Exploitation requires user interaction, and successful exploitation runs attacker-controlled code in the GUIX Studio process.
The record
- CVE
- CVE-2023-36418
- Published
- Oct 10, 2023
- Updated
- Apr 14, 2025
- Vendor
- Microsoft
- Product
- Azure RTOS GUIX Studio
- Classifications
- CWE-415, T1204
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 10, 2023CVE publishedPublication date reported by the CVE source.
- Apr 14, 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=6.0.0.0 <6.3.0
- Affected versionversion=6.0.0 <6.3.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.
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