CVE-2022-24408 json
A vulnerability has been identified in SINUMERIK MC (All versions < V1.15 SP1), SINUMERIK ONE (All versions < V6.15 SP1).
published 2022-03-08 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-29300
- cvss
- 7.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 11%
- public exploits
- 0
- none known
Summary
A vulnerability has been identified in SINUMERIK MC (All versions < V1.15 SP1), SINUMERIK ONE (All versions < V6.15 SP1). The sc SUID binary on affected devices provides several commands that are used to execute system commands or modify system files. A specific set of operations using sc could allow local attackers to escalate their privileges to root.
Patch / fix
- siemens sinumerik_mc_firmware 1.15
- siemens sinumerik_one_firmware 6.15
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-22-069-11 updated cvss 7.8
Siemens SINUMERIK MC
-
Siemens SINUMERIK MC <V1.15_SP1affected: fixed in V1.15
-
Siemens SINUMERIK ONE <V6.15_SP1affected: fixed in V6.15
Facts from CISA's republication of the vendor's own advisory (CSAF); the linked advisory is the authoritative source. CISA notification · csaf
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
Affected products
- Siemens SINUMERIK MC
- Siemens SINUMERIK ONE
Classification
- Weakness
-
- CWE-269 Improper Privilege Management
References
-
cert-portal.siemens.com
/productcert/pdf/ssa-337210.pdf
mitigation, vendor-advisory
Sources
- CVE List CVE-2022-24408
- NVD CVE-2022-24408
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.