CVE-2024-22042
Siemens Unicam Fx
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-22042 is a high-severity Incorrect Use of Privileged APIs (CWE-648) vulnerability in Siemens Unicam Fx. Its CVSS base score is 7.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Protocol or Service Impersonation (T1001.003); ranked at the 4th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-19645
Vulnerability Data
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…
more
be exploited by an attacker to perform a local privilege escalation attack.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V3.5.2V6.4.6
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover incorrect calls to privileged APIs before deployment.
Enforces authorization checks around privileged operations so that an API requiring elevated rights cannot be reached or misused without proper rights.
Least-privilege assignment directly reduces both the availability of privileged APIs and the blast radius when they are invoked incorrectly.
Security engineering principles include correct use of privileged interfaces and safe invocation patterns that stop the weakness from being introduced.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly enforce correct usage of privileged APIs during development.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Restricting privileged utility programs limits the exposure of privileged APIs to misuse.
Privileged access rights directly govern the correct use of privileged APIs and reduce misuse.
Secure development lifecycle includes API usage standards that can prevent incorrect privileged calls.
A.8.26 requires that security requirements (including access segregation) be identified during development or acquisition; it does not itself enforce, implement or assure correct use of privileged APIs, so the weakness can still be present and exploitable.
Secure architecture principles guide proper privilege separation and API usage.
Secure coding standards can enforce correct usage of privileged APIs.