CVE-2022-35773
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAzure RTOS GUIX Studio Remote Code Execution Vulnerability
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAzure RTOS GUIX Studio contains a remote code execution vulnerability. GUIX Studio is a visual UI development tool for the Azure RTOS GUIX graphical user interface framework. The vulnerability allows attackers to execute arbitrary code via malicious project files or data processed by the application.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if Azure RTOS GUIX Studio is installedSearch for guix_studio.exe or similar GUIX Studio executables on the system. Common locations: C:\Program Files\Microsoft Azure RTOS GUIX Studio or C:\Program Files (x86)\Microsoft Azure RTOS GUIX Studio. Use file search or check Add/Remove Programs in Windows Control Panel.Affected if The software is found installed on the system, as all versions are vulnerable.
-
Identify the installed versionRight-click the guix_studio.exe file, select Properties, and view the Details tab for version information. Alternatively, run the executable and check Help > About in the application menu.Affected if Any version number is displayed, confirming the vulnerable software is present.
-
Check for recent project file processingExamine the application data folder for recently opened .gxp project files. Default locations: %APPDATA%\Microsoft\AzureRTOSGUIXStudio\ or within user documents folders.Affected if There are any .gxp project files present, indicating the application has processed project data that could contain malicious payloads.
-
Review application execution historyCheck Windows Event Viewer for recent executions of guix_studio.exe, or review browser/download history if project files were obtained from external sources.Affected if The application was recently opened, especially if used to process files from untrusted sources.
If Azure RTOS GUIX Studio is installed on the system (any version), the environment is affected by this vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply Microsoft security updates for Azure RTOS GUIX Studio when available. Limit exposure by running GUIX Studio in isolated environments and avoid opening untrusted project files.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-35773 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-35773 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data