Unicam FxApplication · Siemens

CVE-2024-22042

HIGH · 7.8 CVSS v3.1 Published 2024-02-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
A vulnerability has been identified in Unicam FX (All versions). The windows installer agent used in affected product contains incorrect use of privileged APIs that trigger the Windows Console Host (conhost.exe) as a child process with SYSTEM privileges. This could be exploited by an attacker to perform a local privilege escalation attack.

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 · high confidence

The Unicam FX windows installer agent incorrectly uses privileged APIs that spawn the Windows Console Host (conhost.exe) as a child process running with SYSTEM privileges. This improper use of elevated privileges can be exploited by a local attacker to gain unauthorized SYSTEM-level access.

MitigationApply vendor patches when available. Until then, restrict installer execution to privileged administrators only and monitor for suspicious conhost.exe child processes spawned by the installer.

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 data
Unicam FxApplication
Affected:all versions

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Siemens Unicam FX is installed
    Open Windows Registry and look under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry containing 'Unicam FX' or check C:\Program Files\Siemens\Unicam FX for the installation directory.
    Affected if The software is present on the system, indicating the vulnerable installer agent exists.
  2. Locate the Unicam FX installer executable
    Search for installer files named similarly to 'Unicam FX' or 'UnicamFX' with .exe extension in the installation directory or in a dedicated installer folder.
    Affected if The installer executable exists on the system.
  3. Identify the installer agent process
    When the Unicam FX installer runs, use Task Manager or Process Explorer to observe the process tree. Look for the main installer process spawning conhost.exe as a child process.
    Affected if The installer spawns conhost.exe as a direct child process.
  4. Verify conhost.exe runs with elevated privileges
    In Task Manager or Process Explorer, right-click the conhost.exe process spawned by the installer and check the user account. Look for 'SYSTEM' or other elevated privileges.
    Affected if conhost.exe is running under the SYSTEM account when spawned by the installer.
  5. Monitor for suspicious conhost.exe spawning
    Use Process Monitor (Sysinternals) to set up a filter: Process Name contains 'Unicam' and Operation is 'Process Create'. Observe if conhost.exe is created as a child of any Unicam process.
    Affected if The installer creates conhost.exe child processes, confirming the vulnerable behavior.

If Siemens Unicam FX is installed and its installer process spawns conhost.exe as a child running with SYSTEM privileges, the environment is affected by CVE-2024-22042.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches when available. Until then, restrict installer execution to privileged administrators only and monitor for suspicious conhost.exe child processes spawned by the installer.

Fix this in Unicam Fx Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-22042 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-22042 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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