CVE-2022-35806
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 graphical user interface development tool for embedded systems. The vulnerability likely stems from improper validation of project files, resources, or assets parsed by the Studio application, potentially allowing an attacker to execute arbitrary code through maliciously crafted input.
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.
-
Confirm if Azure RTOS GUIX Studio is installedSearch for GUIX Studio in installed programs on Windows (check Program Files, Program Files x86, or look in Start Menu). On Windows, you can also run 'Get-ItemProperty' in PowerShell for registry keys under HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or check for the guix_studio.exe binary.Affected if The application is present on the system.
-
Identify the installed versionRight-click on guix_studio.exe if found, select Properties, then view the Details tab for version information. Alternatively, run the executable with a --version flag if supported, or check the product documentation installed alongside.Affected if Any version is returned, since all versions are affected.
-
Locate recent project filesSearch the file system for .gx (or other GUIX project file extensions) that may have been opened recently. Check the user's recent documents or project directories associated with GUIX Studio.Affected if Any project files from untrusted or unknown sources have been opened with GUIX Studio.
-
Review execution logs or crash reportsCheck application event logs, GUIX Studio logs in its installation directory, or any crash dump files for unexpected behavior, especially related to file parsing operations.Affected if Logs indicate crashes or unexpected behavior when opening project files.
If Azure RTOS GUIX Studio is installed on the system, the environment is affected since all versions contain the vulnerability and the attack vector involves opening maliciously crafted project files.
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 available vendor patches for Azure RTOS GUIX Studio. If no patch is immediately available, restrict network access to the Studio development environment and exercise extreme caution when opening project files from untrusted sources.
- Consultation6.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-35806 — 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-35806 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