Security Resilience

CVE-2023-28832

RCE in Siemens 6Gk1411-1Ac00 Firmware 2.0

Published
09 May 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 7.2
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.015 74th percentile
Risk Priority 56 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-28832 is a high-severity Command Injection (CWE-77) vulnerability in Siemens 6Gk1411-1Ac00 Firmware. Its CVSS base score is 7.2 (High).

Operationally, ranked in the top 26% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A vulnerability has been identified in SIMATIC Cloud Connect 7 CC712 (All versions >= V2.0 < V2.1), SIMATIC Cloud Connect 7 CC716 (All versions >= V2.0 < V2.1). The web based management of affected devices does not properly validate user…

more

input, making it susceptible to command injection. This could allow an authenticated privileged remote attacker to execute arbitrary code with root privileges.

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-29103Same product: Siemens 6Gk1411-1Ac00
CVE-2023-29106Same product: Siemens 6Gk1411-1Ac00
CVE-2023-29105Same product: Siemens 6Gk1411-1Ac00
CVE-2023-29104Same product: Siemens 6Gk1411-1Ac00
CVE-2023-29128Same product: Siemens 6Gk1411-1Ac00
CVE-2023-29107Same product: Siemens 6Gk1411-1Ac00
CVE-2024-39567Same vendor: Siemens
CVE-2023-36750Same vendor: Siemens
CVE-2023-36752Same vendor: Siemens
CVE-2024-56836Same vendor: Siemens

Affected Assets

siemens
6gk1411-1ac00 firmware
2.0
siemens
6gk1411-5ac00 firmware
2.0

Mitigating Controls

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.

blocks

A.8.25 mandates secure SDLC practices including secure coding guidelines, security requirements, checkpoints, testing (scans/penetration), and developer training that reduce command injection defects, but leaves a minority slice (e.g. incomplete implementation of those practices, outsourced development without full assurance, or post-SDLC changes) where the weakness can still arise and be exploitable.

blocks

Application security requirements explicitly call for controls against injection flaws including command injection.

blocks

A.8.27 mandates security-by-design principles (e.g. distrust external input, secure session control, data validation/sanitization, least privilege) and design reviews that can stop command injection from being introduced, but this is only a minority slice of CWE-77 because the weakness can still arise in code that bypasses those principles, in non-reviewed components, or in runtime injection vectors the architecture review does not reach.

prevents

Secure coding standards require proper escaping and parameterization of commands, directly eliminating CWE-77.

finds

Security testing in development catches command-injection vulnerabilities before release.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-77, a class-level weakness, and none of its children carries one either.

References